show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
CADIN Estadual
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?
The annotations already declare readOnlyHint=true and idempotentHint=true, so the description doesn't contradict them. However, it adds no additional behavioral detail beyond stating that it shows versions, offering no extra context on side effects, output format, or error cases.
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, efficient sentence with no redundant words or filler.
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?
The tool is extremely simple: no parameters, no output schema. The description tells the agent exactly what information is returned (platform and adapter versions), which is sufficient for this level of complexity.
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 input schema has zero properties, and the parameter count is 0, so the baseline is 4. The description doesn't need to document parameters, and it doesn't.
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 the specific verb 'Show' and clearly identifies the resource as 'current MCP platform and adapter versions,' which distinguishes it from other tools that might handle different resources.
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 information is provided about when to use this tool versus alternatives like 'toolkit_info' or 'marketplace.' The description only states the function, not the appropriate context.
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
Disambiguation3/5
Tools like authenticate, connect, and toolkit_info all relate to connection/auth status, which could cause selection confusion. Meanwhile, marketplace is an extremely broad multi-action tool that overlaps conceptually with install and configure functions, though its description is detailed.
Naming Consistency2/5
Naming is inconsistent: single-word tools (authenticate, connect, marketplace) mix with verb_noun patterns (report_bug, show_version), while cadin_estadual_consultar and toolkit_info do not follow a predictable style. This lack of a consistent convention makes the tool set feel disjointed.
Tool Count4/5
With 7 tools, the count is within the typical well-scoped range. However, the mixture of platform management utilities and a single domain-specific query function makes the overall scope ambiguous, slightly reducing the appropriateness.
Completeness2/5
Given the server name 'CADIN Estadual', the tool surface is severely incomplete—there is only one query function with no support for listing states, bulk queries, or managing query history. If the intent is a platform management server, the marketplace tool covers many operations, but the naming suggests a domain-specific service, leaving major gaps.