show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
DAP Pronaf PJ
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4.3/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, fully covering the tool's safety profile. The description adds no extra behavioral context beyond 'show versions,' which is adequate but does not enrich the disclosure further.
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?
A single, front-loaded sentence conveys the complete purpose with no wasted words. It is highly concise and well-structured.
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 extremely simple, and the annotations plus description together fully characterize its behavior. The return value (version information) is obvious from the verb 'show,' and no additional context is needed.
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, and the input schema is empty with 100% coverage. The description correctly implies no inputs are needed, and the baseline for zero-parameter tools is 4.
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 a precise resource ('current MCP platform and adapter versions'), clearly distinguishing it from sibling tools like authenticate, report_bug, or marketplace. It unambiguously states what the tool does.
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?
While it does not mention alternatives or exclusions, the purpose of displaying version information is self-explanatory and distinct from the sibling tools. Clear context is provided for when to use this tool, though no explicit when-not-to-use guidance is given.
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
Tools are mostly distinct, but authenticate and connect both deal with authentication/connection, and connect and toolkit_info both report status. The remaining tools (dap_pronaf_pj_consultar, marketplace, report_bug, show_version) have clear, non-overlapping purposes.
Naming Consistency2/5
Naming is inconsistent: verbs (authenticate, connect, report_bug, show_version) mix with nouns (marketplace, toolkit_info), and the domain tool uses a Portuguese phrase 'dap_pronaf_pj_consultar' that doesn't follow any clear pattern. No consistent convention is applied across the set.
Tool Count4/5
Seven tools is a reasonable count for a server that combines a domain-specific consultation function with platform utilities. It sits within the typical well-scoped range, though the scope is heavily weighted toward platform management rather than domain operations.
Completeness5/5
The domain purpose (DAP consultation by CNPJ) is fully covered by the single domain tool, and the marketplace tool provides access to a vast range of additional MCPs, making the overall surface quite complete. Platform management and feedback channels are also present, so no major gaps are evident.