show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Banco Central do Brasil (BCB): Cotações
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.9/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare read-only and idempotent behavior, and the description's 'Show' is consistent. It adds minimal extra context by specifying 'current' and 'platform and adapter' versions, but does not disclose any further behavioral details such as performance or external dependencies.
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 full purpose of the tool.
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?
Given the tool's simplicity (zero parameters, no output schema), the description is complete enough for an agent to understand what it returns and when to use it. The annotations cover safety, making this a self-contained and adequate description.
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 schema coverage is vacuously 100% and no parameter explanation is needed. Per the baseline for 0 params, a score of 4 is appropriate.
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 a clear resource ('current MCP platform and adapter versions'), unambiguously stating the tool's function. It distinguishes itself from sibling tools by focusing on version information rather than generic 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 Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided for when to use this tool versus alternatives like toolkit_info. The description only states what it does, not when it should be chosen over siblings, leaving the agent to infer usage from 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
Most tools are clearly separated (report_bug, show_version, toolkit_info), but authenticate and connect overlap around credentials/connection status, and marketplace's invoke capability could be confused with the BCB query tool for running data lookups. The line between 'using the platform' and 'querying BCB data' is not crisp.
Naming Consistency2/5
Naming conventions are mixed: bare verbs (connect), English verb_noun pairs (report_bug, show_version), nouns (marketplace, toolkit_info), and one Portuguese noun_verb construction (bcb_cotacoes_consultar). There is no consistent pattern across the set.
Tool Count3/5
Seven tools is a reasonable count by number, but six of them are generic platform/utility tools (marketplace, connect, authenticate, etc.) with only one BCB-specific tool. The set is not tightly scoped to the server's stated purpose of BCB quotes.
Completeness3/5
For the actual BCB domain, only one query tool exists; it may cover basic quote lookups but there is no dedicated tool for enumerating available series, currencies, or historical ranges. The core read path exists, but the domain surface feels thin.