show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Mercado Financeiro BR
TDQS
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds minimal behavioral context (e.g., 'current' versions) but does not disclose details like whether a network call is made or the exact output structure. This is acceptable given the safety hints, but no extra value is provided.
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, clear sentence that immediately states the tool's action and target. There is no redundant or extraneous information, exemplifying excellent conciseness.
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 version-query tool, the description covers the essential purpose. It doesn't specify the exact return format, but the lack of an output schema and the tool's simplicity make this minor gap acceptable. The tool is clearly a low-complexity read operation.
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, and the schema coverage is effectively 100%. The baseline of 4 applies because the description has no parameter burden. It simply states the tool's purpose without needing to explain any inputs.
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 identifies the exact resources ('current MCP platform and adapter versions'), making the tool's purpose unambiguous. It distinguishes itself from sibling tools like 'toolkit_info' by focusing specifically on version information.
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?
The description implies use when version information is needed but provides no explicit guidance on when to use this tool versus alternatives. There are no exclusions or alternative tool references, though the purpose is obvious enough for a simple version query.
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.9/5.0
Disambiguation5/5
Each tool has a clearly distinct purpose: authenticate and connect are separate (login vs status), the mercado_* tools each target a specific asset class or function (crypto, currency, listing, macro, quote, ticker search), and platform tools like marketplace, report_bug, show_version, and toolkit_info are unambiguous. There is no meaningful overlap that would cause an agent to select the wrong tool.
Naming Consistency3/5
The naming is mixed: financial tools consistently use the 'mercado_' prefix, but platform tools use a variety of conventions—single words (authenticate, connect, marketplace), verb_noun with underscores (report_bug, show_version), and nouns (toolkit_info). While readable, this inconsistency is noticeable and not as uniform as a strong verb_noun pattern.
Tool Count4/5
At 12 tools, the count is within a reasonable range, but roughly half of the tools are platform-management concerns (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) rather than financial data. This makes the set feel heavier and less focused than a pure market-data server, though it's not excessive.
Completeness4/5
The financial data tools cover a broad range: quotes, screening, crypto, exchange rates, macro indicators, and ticker discovery—sufficient for a Brazilian market data server. Some potential gaps like news or portfolio management are out of scope, and the platform tools add extra utility, leaving no critical missing operations for the core purpose.