show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Copa do Mundo 2026
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4.1/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is clear. The description adds the object scope (platform and adapter) and 'current' dynamic nature, but does not describe output format or other behavioral details. No contradiction found.
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 with no wasted words. It efficiently conveys the tool's purpose.
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 version-check tool with strong annotations, the description is complete. The return value is self-evident, and no output schema is necessary to understand the tool's behavior.
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. No parameter explanation is needed, and the description does not need to add parameter meaning.
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 clearly states the specific action ('Show') and the exact resource ('current MCP platform and adapter versions'). It fully explains what the tool does and distinguishes it from siblings like authenticate or toolkit_info.
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 when-to-use guidance or alternative tool is mentioned. The usage is implied by the version-query purpose, but the description does not explicitly articulate when the agent should choose this over other tools.
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
Disambiguation4/5
The World Cup tools (worldcup_bracket, worldcup_groups, worldcup_matches, etc.) are clearly distinct with specific usage examples. The platform tools (authenticate, connect, marketplace, etc.) are also distinct, though connect and toolkit_info have some overlap in reporting connection status. Overall, agents should select the correct tool with minimal ambiguity.
Naming Consistency3/5
The eight World Cup tools follow a consistent 'worldcup_<noun>' pattern, but the six platform tools use mixed conventions: verbs (authenticate, connect), noun phrases (marketplace, toolkit_info), and verb_noun (report_bug, show_version). This inconsistency across the two groups hurts overall coherence, even though each group is internally consistent.
Tool Count4/5
With 14 tools, the count is within the recommended range. It covers both the platform management surface (6 tools) and the World Cup data domain (8 tools). The number feels justified for the server's dual purpose, though it could be seen as slightly heavy for a single focused use case.
Completeness4/5
The World Cup tools provide comprehensive coverage: teams, groups, matches, results, schedule, standings, bracket, and venues—no obvious gaps for a tournament information server. The platform tools cover auth, connection, marketplace, version, bug reporting, and toolkit state, which is complete for their purpose. Minor missing features like player stats or news are not essential.