show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Regularidade de Transportadora ANTT
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, and non-destructive. The description adds specific detail about the two version categories (platform and adapter), which is useful beyond the generic annotations. No additional behavioral traits are needed for such a simple read operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence that front-loads the action and resource. Every word adds value, with no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity, zero parameters, rich annotations, and lack of an output schema, the description is complete enough for an agent to select and invoke the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the baseline of 4 applies. The description correctly does not attempt to describe parameters that do not exist.
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?
The description uses a specific verb 'show' and names the resource ('MCP platform and adapter versions'). It clearly distinguishes the tool from siblings like authenticate or report_bug, which have different purposes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The context is clear: use to display version information. No exclusions or alternatives are mentioned, but the tool's purpose is self-evident and differentiation from siblings is implicit through the specialization.
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.
TDQS
A3.9/5.0
Disambiguation4/5
The single domain tool (antt_transportadora_consultar) is clearly distinct from the platform utilities. However, connect and toolkit_info both report connection/status information, creating slight overlap. The other tools serve separate purposes (auth, marketplace, bug reporting, version).
Naming Consistency2/5
Tool names are inconsistent in style: the domain tool uses a long snake_case prefix, while the platform tools use short verbs (authenticate, connect), noun phrases (marketplace, toolkit_info), or verb_noun (report_bug, show_version). No clear pattern ties them together.
Tool Count3/5
With 7 tools, the count is reasonable, but the composition is unbalanced—only one tool directly serves the ANTT domain while the other six are generic platform/management tools. The set feels like a standard wrapper with a single domain functionality tacked on.
Completeness4/5
For the stated purpose of querying ANTT carrier regularity, the single consult tool covers the essential operation (by CPF, CNPJ, or RNTRC). It lacks any supplementary domain actions, but the core query is fully addressed. The platform tools fill typical admin needs, so no critical gaps for the primary use case.