Skip to main content
Glama

BRAINIAC Agent Tool Schema Intelligence

Detect ambiguous tool schemas

agent-tool-schema_tool-schema-ambiguity-detect
Read-onlyIdempotent

Flag generic tool names, generic parameter names, and descriptions that repeat the name or are missing. Matching is against a fixed word list, not a language model. Price $0.03 USDC. POST /api/v1/agent-tool-schema/tool-schema-ambiguity-detect. 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-ambiguity-detect"
  }
}

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?

The description adds real behavior beyond the readOnly/idempotent/non-destructive annotations: the detection is keyword-list based rather than model-based, the call costs $0.03 USDC, and an unpaid call returns x402 payment terms without executing. Those payment and determinism traits are not derivable from the annotations or schema. It stops short of describing result shape or word-list scope, but the payment gating disclosure is substantial.

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?

The detection criteria are front-loaded in the first sentence, followed by method, price, endpoint, and payment behavior. Every sentence carries information, though the raw endpoint path is arguably operational detail rather than selection guidance. It is compact and well ordered overall.

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?

For a read-only analysis tool with an output schema available, the description covers what is checked, the matching method, pricing, and the unpaid-call failure mode. It doesn't explain what the response contains or how findings are structured, but the output schema covers the return values. Adequate for the tool's complexity.

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 coverage is nominally 100%, but the schema descriptions are tautological ('tools, array. Optional.'), so the schema itself conveys little meaning. The description adds nothing about the three parameters (tools, openapi, schemas) or how each input mode is used. Baseline 3 applies when the schema is the documented surface, though the opportunity to clarify input modes was missed.

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 names specific things it flags: generic tool names, generic parameter names, and descriptions that repeat the name or are missing. That goes beyond the title and tells the agent concretely what counts as ambiguous. It doesn't explicitly contrast itself with siblings such as tool-schema-description-score or tool-schema-lint, so it falls short of a 5.

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 line 'Matching is against a fixed word list, not a language model' implicitly tells the agent when this check applies: fast, deterministic keyword heuristics rather than semantic scoring. However, there is no explicit when-to-use, when-not-to-use, or named alternative, so guidance remains implied rather than stated.

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