Skip to main content
Glama

BRAINIAC Agent Tool Schema Intelligence

Validate tool request examples

agent-tool-schema_tool-schema-example-validate
Read-onlyIdempotent

Check caller-supplied request examples against their JSON Schema types, required fields, enums, and bounds. External schema URLs are not fetched. Price $0.04 USDC. POST /api/v1/agent-tool-schema/tool-schema-example-validate. An unpaid call returns the x402 payment terms and does not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "agent-tool-schema_tool-schema-example-validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolsNotools, array. Optional.
openapiNoopenapi, object. Optional.
schemasNoschemas, array. Optional.

Output Schema

NameRequiredDescriptionDefault
scoreNoscore. Number.
issuesNoissues. Array.
successNosuccess. Boolean.
analysisNoanalysis. String.
warningsNowarnings. Array.
limitationsNolimitations. Array.
recommendationsNorecommendations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive semantics, so the bar is lower. The description still adds real operational context beyond them: no external URL resolution, a fixed price of $0.04 USDC, and the fact that an unpaid call returns x402 payment terms without executing. That unpaid-call behavior is exactly the kind of trait 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.

Conciseness4/5

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

Four short sentences, front-loaded with the validation scope, then constraints, then commercial/transport details. The endpoint path and price are arguably logistics rather than semantics, but they are compact and genuinely useful for an agent that must decide whether to call a paid endpoint.

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

Completeness4/5

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

Output schema exists and need not be explained, and the description supplies the missing pieces an agent needs before calling: what is validated, what is not fetched, and what happens without payment. Only the routing decision against sibling schema-checking tools remains unaddressed.

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 tools, schemas, and openapi plus nested name/examples/inputSchema fields; baseline 3 applies. The description adds only the indirect hint that 'request examples' are the payload checked, and never mentions the schemas array or openapi object that the schema exposes.

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?

Starts with a specific verb and resource: 'Check caller-supplied request examples against their JSON Schema types, required fields, enums, and bounds.' That is far more precise than the title alone and lets an agent distinguish this from lint or ambiguity-detection siblings, though it never names a sibling explicitly.

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 when this applies (you have request examples and want schema conformance checks) and gives one real exclusion: external schema URLs are not fetched. It does not say when to prefer this over tool-schema-lint or compatibility-check, so an agent must infer the boundary from names alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources