show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Servidores Federais Completa (Transparência)
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.9/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds that it shows versions but does not disclose additional behavioral traits such as return format or any side effects. It is consistent with annotations.
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 or filler.
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?
For a zero-parameter, read-only version-information tool, the description is complete. The annotations cover safety, and the simple purpose is fully conveyed without needing additional detail.
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 is 4. The description adds no parameter information, but none is needed since the input schema is empty and thus fully covered.
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 clearly identifies the resource as 'the current MCP platform and adapter versions.' This distinguishes it from sibling tools like authenticate or marketplace, making the purpose unambiguous.
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?
No explicit guidance is provided on when to use this tool versus alternatives, nor are there any exclusions or conditions. The usage is only implied by the tool's name and description.
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.4/5.0
Disambiguation2/5
Several tools have overlapping responsibilities: 'connect' and 'toolkit_info' both return connection/status info, 'authenticate' handles session/auth concerns, and 'marketplace' bundles numerous actions (including install, subscribe, cancel, report_bug) that duplicate capabilities of 'report_bug' and other tools. Agents would struggle to choose the right tool without examining internal action parameters.
Naming Consistency2/5
Tool names follow no consistent pattern: some are bare verbs ('authenticate', 'connect'), some are verb_noun ('report_bug', 'show_version'), one is a noun ('marketplace'), and the domain-specific tool uses a long Portuguese composite ('transparencia_servidores_completa_consultar'). The mix of English platform verbs and a Portuguese domain name adds inconsistency.
Tool Count3/5
Seven tools is within an acceptable range, but the 'marketplace' tool is a monolithic catch-all containing search, describe, invoke, install, list, subscribe, cancel, report_bug, request_mcp, and prompt management, effectively representing 12+ operations under one tool. This makes the actual surface area much larger than the count suggests, though the number itself is reasonable.
Completeness2/5
The server's stated purpose is federal employee transparency, but only a single CPF query tool is provided, with no listing, filtering, or batch operations. The platform admin tools (authenticate, connect, marketplace, etc.) are comprehensive, but they don't cover the transparency domain, which appears to be the server's primary focus. Many common transparency needs remain unsupported.