show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Itaú MCP
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds that it shows specific version details (platform and adapter), which is consistent and adds context.
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?
One sentence, perfectly concise with no waste. Every word is meaningful.
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 simple version display tool with no parameters and clear annotations, the description fully covers what an agent needs to know.
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?
No parameters exist (schema coverage 100%). The description adds value by indicating the output contains platform and adapter versions, beyond the empty schema.
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 it shows MCP platform and adapter versions, distinguishing it from sibling tools that handle authentication, finance operations, and other tasks.
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 description implies use for version checking, but does not explicitly state when to use or provide alternatives. However, given its simplicity, it is clear that it can be used at any time without side effects.
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
A4/5.0
Disambiguation3/5
The Open Finance tools have clear list/get pairs for each resource (accounts, transactions, loans, investments, bills), but the marketplace tool is a monolith combining search, describe, invoke, install, subscribe, and prompt library actions, causing ambiguity about which action to use. Additionally, openfinance_list_transactions and openfinance_list_transactions_by_item overlap in purpose but are distinguished by scope.
Naming Consistency3/5
The openfinance_* group follows a consistent verb_noun pattern (list, get, update, force_sync, etc.), but the platform tools (authenticate, connect, marketplace, show_version, report_bug, toolkit_info) use mixed bare verbs and nouns, creating two distinct conventions. Names like openfinance_list_transactions_by_item are longer but still consistent within the group.
Tool Count4/5
25 tools is at the heavy end, but the Open Finance domain alone justifies 17 tools covering distinct resources and operations. The platform tools add 8 more, though the marketplace tool bundles many sub-actions into one, inflating the effective count. The number is borderline but not excessive given the breadth of banking functionality.
Completeness5/5
The Open Finance surface is comprehensive with list/get for every major resource, plus support for sync, status, search, categories, and category updates. The platform tools cover authentication, connection status, marketplace operations, bug reporting, version, and toolkit state. No obvious gaps or dead ends in the workflow.