Skip to main content
Glama

BRAINIAC Agent Tool Schema Intelligence

Check tool schema dialect compatibility

agent-tool-schema_tool-schema-compatibility-check
Read-onlyIdempotent

Report JSON Schema keywords that the caller-selected dialect does not allow. Targets are draft-07, 2020-12, OpenAPI 3.0, and OpenAPI 3.1. The schema is not sent to a validator service. Price $0.04 USDC. POST /api/v1/agent-tool-schema/tool-schema-compatibility-check. 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-compatibility-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolsNotools, array. Optional.
targetNotarget, string. 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.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, but the description adds genuinely new behavior: the schema is not sent to an external validator service, the call costs $0.04 USDC, and an unpaid call returns x402 payment terms without executing. That payment-gating detail is important and not derivable from annotations. It stops short of describing error or partial-failure behavior when multiple targets are supplied.

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 sentences, front-loaded with the purpose and supported targets, then behavior, then price and endpoint. Every sentence carries distinct information with no repetition, though the price/endpoint/payment sentences could be consolidated slightly.

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?

Return values are covered by the existing output schema, so the description needn't explain them, and it does address safety, cost and payment gating. But for a tool with four all-optional, ambiguously named parameters plus nested objects, it offers no guidance on which parameters matter or how to combine them, leaving a real gap.

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 structured schema already carries the parameter documentation and baseline 3 applies. The description adds no meaning about the opaque parameters (tools, schemas, openapi, target) or how target relates to openapi, so it neither compensates for nor improves on the schema.

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?

States a specific verb and resource: 'Report JSON Schema keywords that the caller-selected dialect does not allow', and enumerates the four supported dialect targets. This is clearly a compatibility check, not a lint or ambiguity scan, so an agent can separate it from siblings like tool-schema-lint or tool-schema-ambiguity-detect without opening schemas.

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?

Usage is implied by the enumerated targets (the tool is for checking a schema against draft-07, 2020-12, OpenAPI 3.0 or 3.1), which is enough to know when it applies. However, there is no explicit when-to-use versus the sibling lint/ambiguity/required-field tools, and no statement of prerequisites such as needing the target dialect argument.

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