show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Protestos Nacional
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4/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 agent knows this is a safe, read-only, idempotent operation. The description adds no additional behavioral context beyond stating what it shows (versions), so it does not exceed the information provided by 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, declarative sentence that directly states the function with no wasted words. It is front-loaded and easy to parse.
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 simple tool with no parameters and no output schema, the description is mostly complete. However, it doesn't specify the output format or the source of version information, which could be useful context for the agent.
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 no parameter explanation is needed. Per guidelines, 0 params gives a baseline of 4, and the description correctly makes no parameter references.
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 exact resource: current MCP platform and adapter versions. This clearly distinguishes it from sibling tools like authenticate or marketplace, 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 Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance is given on when to use this tool versus alternatives, such as toolkit_info which might also provide platform information. The usage is implied by the tool's name and description, but no exclusions or alternative recommendations are 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.6/5.0
Disambiguation4/5
Most tools have clearly distinct purposes: authentication, connection status, marketplace discovery/execution, domain lookup, bug reporting, version info, and toolkit state. There is minor overlap between authenticate and connect, but their descriptions clarify the different concerns.
Naming Consistency2/5
Tool names follow no consistent pattern: single verbs (authenticate, connect), a noun (marketplace), a contextual object-action (protestos_nacional_consultar), and verb-noun combinations (report_bug, show_version, toolkit_info) are mixed without a unified convention.
Tool Count3/5
Seven tools is within a reasonable range, but the server is dominated by platform meta-tools with only one domain-specific tool, making the tool count feel unbalanced for a server named 'Protestos Nacional'.
Completeness3/5
The single protestos consultation tool covers basic lookup needs, but the domain surface is very thin with no additional operations like history, export, or batch queries. The meta-tools provide broader platform capabilities but do not fill domain-specific gaps.