Skip to main content
Glama

BRAINIAC Agent Tool Schema Intelligence

Score tool description clarity

agent-tool-schema_tool-schema-description-score
Read-onlyIdempotent

Score whether a tool description states a purpose, inputs, outputs, and when to use it. The checks are phrase and length rules, not a language-model reading. Price $0.03 USDC. POST /api/v1/agent-tool-schema/tool-schema-description-score. 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-description-score"
  }
}

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.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and non-destructive, and the description goes beyond them with the paid-access model: $0.03 USDC, the POST endpoint, and the fact that an unpaid call returns x402 payment terms without executing. Disclosing that scoring is rule-based rather than model-judged is also valuable for interpreting results, though it does not describe the response shape or latency.

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 purpose is front-loaded in the first sentence, followed by method, price, endpoint, and payment behavior, with no filler. The endpoint path is partly redundant with the tool name but serves as a usable call detail.

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?

With an output schema present, return values need not be explained, and the payment path is well covered. What is missing is input guidance for a nested-object tool with three optional parameters: the description never says which inputs are required to get a meaningful score, which leaves a real gap for correct invocation.

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 baseline is 3. However, the schema is mostly open objects ('tools' array, 'openapi' object, 'schemas' array) and the description never clarifies which of these must be supplied or how they relate, so it adds no meaning beyond the structured field labels.

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?

States a specific verb and resource ('Score whether a tool description states a purpose, inputs, outputs, and when to use it') and names the exact criteria being measured. It also distinguishes the method ('phrase and length rules, not a language-model reading'), but it never positions itself against siblings such as lint or ambiguity-detect, so an agent must infer the boundary.

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 only implied: the tool checks description quality, so call it when you want a description scored. There is no explicit when-to-use, no when-not-to-use, and no named alternative among lint, ambiguity-detect, or token-cost, even though those overlap conceptually.

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