show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
DETRAN PE: Veículo
TDQS
A4.1/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering safety. The description adds minimal extra context (that it reports current versions) but does not elaborate on potential side effects or data sources. It is adequate but not enriched.
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 short sentence that conveys the essential function without verbosity. It is efficient and to the point.
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?
The tool is simple, with no parameters and no output schema. The description fully covers its purpose and does not require additional context. It is complete for its intended use.
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?
There are no parameters, so the baseline score is 4. The description adds no parameter-related information, but since none exist, it is appropriate.
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 clearly states the tool's purpose: to show current MCP platform and adapter versions. It is specific and unambiguous, and it distinguishes itself from other tools by focusing on version information only.
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 description does not explicitly state when to use this tool versus alternatives, but the purpose is self-evident. Usage is implied: whenever version info is needed. No exclusion or comparison with other tools is provided.
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.6/5.0
Disambiguation4/5
The tool set contains one domain-specific tool (detran_pe_veiculo_consultar) and several platform utilities. Most have distinct purposes, but connect and toolkit_info both report connection status, which could cause minor confusion. Overall, the tools are well-separated.
Naming Consistency2/5
Tool names mix English and Portuguese, and use inconsistent structural patterns. For example, 'marketplace' is a noun while 'authenticate' is a verb, and 'detran_pe_veiculo_consultar' follows a Portuguese naming convention. This inconsistency makes it harder to predict tool names.
Tool Count3/5
With 7 tools, the count is within a reasonable range, but the server's specific name suggests a focus on DETRAN PE vehicle data, yet only one tool directly addresses that. The remaining tools are generic platform utilities, which dilutes the server's apparent purpose.
Completeness2/5
The only domain-specific tool is a single query operation for DETRAN PE vehicles. No other vehicle-related operations are present, such as lookup by different identifiers, history, or fines. The platform utilities are comprehensive but do not contribute to the data domain, leaving the DETRAN coverage extremely thin.