Skip to main content
Glama

BRAINIAC Agent Tool Schema Intelligence

Audit tool required fields

agent-tool-schema_tool-schema-required-field-audit
Read-onlyIdempotent

Find required names that are not properties, repeated required names, and required fields that also declare a default. The audit uses only the supplied schema. Price $0.03 USDC. POST /api/v1/agent-tool-schema/tool-schema-required-field-audit. 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-required-field-audit"
  }
}

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

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false), so the description's real contribution is the cost ($0.03 USDC), the transport (POST endpoint), and the failure mode: an unpaid call returns x402 payment terms and performs no work. That payment/failure disclosure is exactly the kind of context annotations cannot express. Missing only a hint about what the audit result looks like, which the output schema likely covers.

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 and the scoping constraint follows immediately; nothing is buried. The raw endpoint string is the least actionable sentence for an agent, but it is a single short clause and does not undermine the otherwise tight structure.

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 nested-object, read-only audit tool with an output schema and full parameter documentation, the description supplies purpose, input scope, price and payment-failure behavior. The one gap is that zero parameters are required, so the description could state what an empty request yields — but that is minor given the output schema exists.

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 three top-level parameters (tools, schemas, openapi) are already documented in the schema, and the baseline is 3. The description adds no semantics about precedence between schemas and tools, or about what happens when both or neither are supplied, so it does not exceed the baseline.

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 a specific verb (audit/find) and enumerates exactly the three defects detected: required names missing from properties, duplicated required names, and required fields that also declare a default. That is far more precise than a generic 'lint' claim. It stops short of distinguishing itself from siblings such as tool-schema-lint or tool-schema-ambiguity-detect, so an agent must infer the boundary from names alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the analysis is purely static ('uses only the supplied schema'), which implicitly tells the agent no live tool invocation is needed. However, there is no explicit when-to-use/when-not guidance and no reference to the sibling audits, so the agent gets no help choosing among lint, ambiguity-detect, overlap-detect and this tool.

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