Why should you care?

Hospital assistants need allergy and medication plugins separated so RBAC can disable whole groups per role.

See it live — copy this example

Paste into an ASP.NET Core 8+ / AgentNest project, then run with dotnet run (set your API keys in user-secrets).

// AgentNest.Plugins/Hospital/AllergyPlugin.cs
public sealed class AllergyPlugin(IAllergyRepository repo)
{
    [KernelFunction, Description("List patient allergies by MRN")]
    public async Task<string> ListAsync(string mrn, CancellationToken ct)
    {
        var items = await repo.GetByMrnAsync(mrn, ct);
        return string.Join("; ", items.Select(a => a.Substance));
    }
}

What happened?

• Description helps the model choose ListAsync.
• The plugin returns a compact string the LLM can cite in triage summaries.

Practice next

1. Create AllergyPlugin in AgentNest.Plugins.
2. Register with builder.Plugins.AddFromObject(new AllergyPlugin(repo), "allergy").
3. Enable auto tool calling in agent loop for hospital queries.
4. Add SearchByIngredient kernel function for drug checks.
5. Wrap repo calls with audit logging.

Remember

Plugins group KernelFunctions by domain. Descriptions guide automatic tool selection. Keep plugin outputs minimal and redacted.

Role-based plugin sets

Nurses see allergy plugin; billing clerks do not.

Outcome: TenantAiContext.AllowedPlugins filters kernel registration at startup.