show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
DETRAN DF: Débitos
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.8/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds that it shows platform and adapter versions, but doesn't disclose any additional behavioral traits like network calls or potential errors. It doesn't contradict annotations, but doesn't add much beyond them.
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?
Single sentence, front-loaded, no filler. Exactly as concise as needed.
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 version info tool with no params and clear annotations, the description is sufficient. It states what it does. It doesn't specify output format, but that's minor.
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 0 parametershola, so baseline is 4. The description doesn't need to add parameter semantics because there are none.
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 action (show) and the resource (current MCP platform and adapter versions). It is specific and distinguishes this tool from siblings like connect or authenticate, which serve entirely 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 Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when it's appropriate to call, nor does it exclude any situations. There is no mention of prerequisites or exclusions, leaving the agent without usage context beyond the name.
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
B3.3/5.0
Disambiguation4/5
Each tool has a distinct purpose: authenticate handles token login, connect checks provider status, detran_df_debitos_consultar queries debts, marketplace searches/executes MCPs, report_bug sends feedback, show_version displays versions, and toolkit_info lists toolkit state. There is minor overlap between authenticate and connect (both deal with connection/auth) and between marketplace and toolkit_info (both involve MCP discovery), but the descriptions are clear enough to avoid major confusion.
Naming Consistency3/5
All tool names are lowercase with underscores, but they do not follow a consistent pattern. Some are verbs (authenticate, connect, report_bug, show_version), some are nouns (marketplace, toolkit_info), and detran_df_debitos_consultar mixes a domain prefix with a verb at the end, using Portuguese rather than English. This inconsistency reduces predictability.
Tool Count2/5
With 7 tools, the count is not extreme, but the scope is mismatched to the server's stated purpose ('DETRAN DF: Débitos'). Only one tool is actually related to DETRAN debts; the other six are generic platform utilities (authentication, marketplace, feedback, etc.). This feels like a general-purpose MCP platform server rather than a focused debt-consultation server, making the tool set inappropriate for the apparent domain.
Completeness1/5
For a server named 'Débidos', the only domain-specific operation is detran_df_debitos_consultar, which provides a single consultation action. There are no other debt-related operations such as listing, filtering, or paying debts, and the rest of the tools are unrelated to the domain. This is a severely incomplete surface for the stated purpose.