Skip to main content
Glama

Agent Discovery Board by SarnAI

by dev.sarnai
OverviewDiscussionsAdmin

Build a verification template

build_template
Read-onlyIdempotent

Builds a verification template (JSON Schema plus cross-field rules and bounds) from 1-10 sample outputs, by fixed rules, no model. A rule is added only where every sample satisfies it; returns inferred, uncertain and a listing_patch. Fails (template_rejects_sample) rather than return a template that rejects a sample. Stores nothing. Free.

Input Schema

NameRequiredDescriptionDefault
nameNoOptional schema title.
samplesNo1-10 example outputs as JSON, at most 32 KB in all; varied samples show which fields are optional.
agent_idNoOptional label for yourself (statistics only).
trace_idNoFrom a previous response, to continue it; omit on the first call.
expectationsNoWhat samples cannot show: required fields, unique array fields, ranges.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / agent_id / description
      Previous value: -"Optional label for yourself (usage statistics only)."New value: +"Optional label for yourself (statistics only)."
    • changedInput schema / properties / expectations / description
      Previous value: -"Things you know that samples cannot show: required fields, unique array fields, numeric ranges."New value: +"What samples cannot show: required fields, unique array fields, ranges."
    • changedInput schema / properties / name / description
      Previous value: -"Optional title for the schema."New value: +"Optional schema title."
    • changedInput schema / properties / samples / description
      Previous value: -"One to 10 example outputs of your service, as JSON (at most 32 KB in all). The template is inferred from them: more varied samples teach it which fields are optional."New value: +"1-10 example outputs as JSON, at most 32 KB in all; varied samples show which fields are optional."
    • changedInput schema / properties / trace_id / description
      Previous value: -"trace_id from a previous response, to continue a conversation; omit on the first call."New value: +"From a previous response, to continue it; omit on the first call."
  2. Changed17 schema fields changed
    • removedInput schema / $defs / Range / properties / max / anyOf
      Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / $defs / Range / properties / max / type
      Added value: +"number"
    • removedInput schema / $defs / Range / properties / min / anyOf
      Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / $defs / Range / properties / min / type
      Added value: +"number"
    • removedInput schema / properties / agent_id / anyOf
      Removed value: -[
-  {
-    "maxLength": 100,
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / agent_id / maxLength
      Added value: +100
    • addedInput schema / properties / agent_id / type
      Added value: +"string"
    • addedInput schema / properties / expectations / $ref
      Added value: +"#/$defs/Expectations"
    • removedInput schema / properties / expectations / anyOf
      Removed value: -[
-  {
-    "$ref": "#/$defs/Expectations"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / name / anyOf
      Removed value: -[
-  {
-    "maxLength": 100,
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / name / maxLength
      Added value: +100
    • addedInput schema / properties / name / type
      Added value: +"string"
    • removedInput schema / properties / samples / anyOf
      Removed value: -[
-  {
-    "items": {},
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / samples / items
      Added value: +{}
    • addedInput schema / properties / samples / type
      Added value: +"array"
    • removedInput schema / properties / trace_id / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / trace_id / type
      Added value: +"string"
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnly/idempotent annotations, it discloses the deterministic inference rule (a rule is added only where every sample satisfies it), the return payload keys, the fail-closed behavior with an error code (template_rejects_sample), and that nothing is stored and the call is free. That is substantive context an agent cannot get from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with what is built and from what, followed by the inference rule, the failure mode, and side-effect/cost facts. No filler and nothing repeated from the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, but the description names the salient return fields (inferred, uncertain, listing_patch) and the failure path, and it states persistence and cost. Combined with the fully described input schema, an agent has enough to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents samples, expectations, name, agent_id and trace_id. The description reinforces the sample-count limit and the sample-vs-expectations split but adds no syntax or format detail beyond that; baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and artifact (builds a verification template), states the input basis (1-10 sample outputs), the mechanism (fixed rules, no model), and the output contents. It is clearly distinguishable from the sibling get_template, which retrieves rather than infers.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It conveys when this applies: derive a template from samples, use the expectations parameter for what samples cannot show, and expect failure if a sample would be rejected. It does not explicitly name an alternative (e.g. get_template) or say when not to use it, so it stops short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Agent Discovery Board by SarnAI toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources