Skip to main content
Glama

BRAINIAC Agent Tool Schema Intelligence

Lint agent tool schemas

agent-tool-schema_tool-schema-lint
Read-onlyIdempotent

Find malformed JSON Schema and OpenAPI tool definitions in caller-supplied tools: bad types, required names that are not properties, empty enums, and duplicate tool names. Nothing is fetched. Price $0.03 USDC. POST /api/v1/agent-tool-schema/tool-schema-lint. 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-lint"
  }
}

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

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the price ($0.03 USDC), the HTTP endpoint, and critically that an unpaid call returns x402 payment terms without executing. That payment-gating behavior is operationally essential and is not expressible through readOnlyHint/openWorldHint/idempotentHint. 'Nothing is fetched' also clarifies the tool performs no external retrieval despite openWorldHint.

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 purpose and defect list, then behavior, cost, and transport. Nearly every sentence earns its place; only the raw POST path is spec detail, though it is defensible for an x402 payment flow.

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?

An output schema exists, so return-value explanation is unnecessary, and the input schema covers parameters fully. The description covers safety, cost, and payment gating. The remaining gap is ambiguity about whether findings are reported as a list versus an error, and how the three optional input families interact.

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 nested tools/openapi/schemas structure is already documented in the input schema and a baseline 3 applies. The description adds only the loose phrase 'caller-supplied tools', without explaining how the three input families differ or whether they can be combined.

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 ('Find malformed JSON Schema and OpenAPI tool definitions') and enumerates the exact defect classes it detects (bad types, required names that are not properties, empty enums, duplicate tool names). That enumeration distinguishes it from structural-analysis siblings like ambiguity-detect or compatibility-check without needing to name them.

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 scope hint 'caller-supplied tools' plus 'Nothing is fetched' implies when this applies (inline definitions passed in the request, not remote specs). However, there is no explicit when-to-use/when-not guidance and no routing to alternatives such as the ambiguity or compatibility tools, so the agent must infer selection from the checks listed.

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