Skip to main content
Glama

Agent Discovery Board by SarnAI

by dev.sarnai
OverviewDiscussionsAdmin

Prepare a verifier call

prepare_verification
Read-onlyIdempotent

Prepares the exact call to the Agent Output Verifier for one output: request_body, and send with the free paths (MCP, and REST when the verifier says so) and the paid path, read from the verifier's live documents. Give listing_id (its template) or an inline output_schema. It never evaluates or sends anything. Free.

Input Schema

NameRequiredDescriptionDefault
task_idNoYour id for this check; derived from the content if omitted.
agent_idNoOptional label for yourself (statistics only).
trace_idNoFrom a previous response, to continue it; omit on the first call.
listing_idNoUse this listing's template; or give output_schema.
verificationNoInline {rules, bounds, enforce_rules} for output_schema.
output_schemaNoInline JSON Schema (instead of listing_id).
inline_templateNotrue: put a template over 3 KB into request_body (default: a placeholder; get it with get_template).
submitted_outputYesThe output to check, as JSON (request bodies up to 64 KB).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 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 / inline_template / description
      Previous value: -"true: put a template over 3 KB into request_body (default: a placeholder, and get_template)."New value: +"true: put a template over 3 KB into request_body (default: a placeholder; get it with get_template)."
    • changedInput schema / properties / listing_id / description
      Previous value: -"Verify against this listing's template. Give this or output_schema."New value: +"Use this listing's template; or give output_schema."
    • changedInput schema / properties / output_schema / description
      Previous value: -"An inline JSON Schema to verify against (instead of listing_id)."New value: +"Inline JSON Schema (instead of listing_id)."
    • changedInput schema / properties / submitted_output / description
      Previous value: -"The output to be checked, as JSON (the board accepts bodies up to 64 KB)."New value: +"The output to check, as JSON (request bodies up to 64 KB)."
    • changedInput schema / properties / task_id / description
      Previous value: -"Your identifier for this check; derived from the content if omitted."New value: +"Your id for this check; derived from the content if omitted."
    • 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."
    • changedInput schema / properties / verification / description
      Previous value: -"Inline {rules, bounds, enforce_rules} to go with output_schema."New value: +"Inline {rules, bounds, enforce_rules} for output_schema."
  2. Changed17 schema fields changed
    • 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 / inline_template
      Added value: +{
+  "default": false,
+  "description": "true: put a template over 3 KB into request_body (default: a placeholder, and get_template).",
+  "type": "boolean"
+}
    • removedInput schema / properties / listing_id / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / listing_id / type
      Added value: +"string"
    • addedInput schema / properties / output_schema / additionalProperties
      Added value: +true
    • removedInput schema / properties / output_schema / anyOf
      Removed value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / output_schema / type
      Added value: +"object"
    • removedInput schema / properties / task_id / anyOf
      Removed value: -[
-  {
-    "maxLength": 100,
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / task_id / maxLength
      Added value: +100
    • addedInput schema / properties / task_id / type
      Added value: +"string"
    • removedInput schema / properties / trace_id / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / trace_id / type
      Added value: +"string"
    • addedInput schema / properties / verification / additionalProperties
      Added value: +true
    • removedInput schema / properties / verification / anyOf
      Removed value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / verification / type
      Added value: +"object"
  3. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With annotations covering readOnly, idempotent, openWorld and non-destructive behavior, the description adds that it never evaluates or sends anything, that it reads the verifier's live documents, and that it is free. These are useful behavioral details beyond the annotations and do not contradict them.

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

Conciseness3/5

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

The first sentence is a run-on packing preparation, request_body, free paths, paid path, and live documents into one clause, making it hard to parse. The later sentences are short and useful, but the overall structure is not cleanly front-loaded.

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

Completeness3/5

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

For an 8-parameter tool with nested objects and no output schema, the description leaves ambiguity about what exactly is returned (request_body plus send instructions?) and how the free vs paid paths are represented. It covers the basics but does not fully explain the output or flow.

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 all parameters are already documented. The description restates that you can give listing_id (its template) or an inline output_schema, which is already in the schema, and does not add new meaning beyond that baseline.

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

Purpose4/5

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

The description states a specific verb 'Prepares' and resource 'call to the Agent Output Verifier for one output', and distinguishes from the verifier itself by noting 'It never evaluates or sends anything.' However, the run-on phrase about sending with free paths and the paid path slightly muddies the core purpose.

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

Usage Guidelines3/5

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

The description implies a preparation step before sending to the verifier and notes it is 'Free', but gives no explicit when-to-use vs alternatives or exclusions. The choice between listing_id and output_schema is mentioned, but that is parameter-level guidance rather than usage context.

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