show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Offshore Leaks (ICIJ)
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 provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description's 'Show' aligns with these. The description adds scope detail (platform and adapter versions) but does not disclose additional behavioral traits such as return format or error behavior.
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 sentence with no unnecessary words, fully front-loaded and clearly stating the purpose without any filler.
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, read-only version query, the description fully covers the tool's purpose. No output schema is present, but none is needed for such a simple tool.
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?
There are zero parameters, so the baseline is 4. The schema has empty properties, and the description correctly adds no parameter details since none exist.
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: 'current MCP platform and adapter versions.' This is distinct from sibling tools like authenticate and marketplace, which have 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 Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The context is clear: this tool is for viewing version information. No explicit when-not or alternatives are mentioned, but no sibling tool serves a similar function, so the implicit guidance is sufficient.
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
B3.3/5.0
Disambiguation4/5
The platform tools (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) are each distinct in purpose, and offshore_leaks_consultar is clearly the only data-facing tool. However, the mix of platform utilities with a single domain-specific query could confuse an agent about the server's primary function.
Naming Consistency2/5
Tool names follow no consistent pattern: single-word nouns (connect, marketplace), verb_noun snake_case (offshore_leaks_consultar), and camelCase-like compounds (show_version, toolkit_info). This inconsistency makes the tool set feel haphazard.
Tool Count1/5
With 7 tools but only one actually related to Offshore Leaks, the count is highly inappropriate. The server appears to be a generic MCP platform masquerading as an offshore-leaks data source, so the tool count does not match the server's stated purpose.
Completeness1/5
The offshore-leaks domain is severely underserved: there is only a single query tool (consultar) and no capabilities for retrieving details, listing entities, or any other data operations. The platform tools are irrelevant to the domain, leaving the core functionality almost entirely missing.