show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
CND Imóvel Rural
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 non-destructive behavior, so the description does not need to restate safety. The description adds no extra behavioral context beyond the annotations, but it is consistent with 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?
The description is a single, front-loaded sentence that clearly states the action and target. No wasted words.
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 simple, zero-parameter tool with no output schema, the description fully conveys what the tool does and what the user will get (version info). It is complete enough 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 input schema is trivially complete. Baseline for 0 params is 4; the description correctly implies no arguments are needed.
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 identifies the resource ('MCP platform and adapter versions'), making the tool's purpose immediately clear. It is distinct from sibling tools like toolkit_info, which likely covers broader information, whereas this focuses specifically on versions.
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 does not provide any guidance on when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. It is a simple 'show me versions' tool, but there is no explicit when-to-use context 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.8/5.0
Disambiguation3/5
The domain tool 'cnd_imovel_rural_consultar' is clearly distinct, but the platform tools overlap: 'connect' and 'toolkit_info' both report connection status, and 'marketplace' is a catch-all for searching, invoking, and managing MCPs. Descriptions are detailed, but the boundaries between these utility tools are not always sharp.
Naming Consistency2/5
Tool names mix styles: single verbs (authenticate, connect), nouns (marketplace), verb_noun with underscores (report_bug, show_version), and a long Portuguese snake_case name (cnd_imovel_rural_consultar). There is no consistent pattern, and the language mix (English vs Portuguese) adds to the inconsistency.
Tool Count3/5
With 7 tools, the count is within a reasonable range, but only one tool serves the server's stated domain ('CND Imóvel Rural'). The other six are generic platform utilities, making the set feel bloated with meta-tools rather than focused on the certificate service.
Completeness4/5
For the domain of issuing a negative certificate for a rural property, the single 'cnd_imovel_rural_consultar' tool covers the core operation. There are no obvious missing domain operations (e.g., no need for update or delete). However, the platform tools are unrelated to the domain, which slightly detracts from the overall completeness.