Why should you care?

Explicit JSON schemas let you diff tool surfaces between releases and block deprecated ERP functions at the gateway.

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.Api/Schemas/GlFunctionSchemaExporter.cs
public static class GlFunctionSchemaExporter
{
    public static object Describe(KernelFunction fn) => new
    {
        name = fn.Name,
        description = fn.Description,
        parameters = fn.Metadata.Parameters.Select(p => new { p.Name, type = p.ParameterType?.Name })
    };
}

What happened?

• Describe projects kernel function metadata into OpenAI-compatible schema shapes for documentation and APIM validation.
• Follow the steps below — typing the code yourself is the fastest way to learn.

Practice next

1. Export schemas from GlPlugin functions at startup.
2. Publish schemas to internal wiki for finance reviewers.
3. Compare schema hashes between releases in CI.
4. Add required flags on parameters in exported schema.
5. Version schema bundle at GET /api/ai/tools.

Remember

Function schemas describe tools to the model API. Generate schemas from KernelFunction metadata. Keep function sets small per agent for accuracy.

ERP tool catalog

Finance wants sign-off on which GL tools agents may call.

Outcome: Exported schemas give auditors a readable catalog tied to C# source.