show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Atacadão MCP
TDQS
A4.4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds context beyond annotations by specifying the exact information returned (MCP platform and adapter versions). No contradictions with annotations.
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?
Single, well-formed sentence that is perfectly concise and front-loaded, accomplishing the goal without any wasted words.
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?
Given zero parameters and no output schema, the description adequately explains the tool's behavior. It lacks detail on the exact format of versions, but this is acceptable for a straightforward version display 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?
No parameters exist, so baseline score of 4 applies. The description correctly indicates no input is needed.
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 tool shows current MCP platform and adapter versions, distinguishing it from all sibling tools which perform authentication, data retrieval, or financial operations.
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 is clear about what the tool does and implies it should be used when version information is needed. No exclusion or alternative guidance is necessary given the tool's simplicity.
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.1/5.0
Disambiguation4/5
Tools are largely distinct: openfinance_* tools cover specific resources (accounts, transactions, bills, loans, investments) with clear boundaries. Some overlap exists between list_transactions and list_transactions_by_item, and between status/sync tools (get_item_status, force_sync, provider_status), but descriptions are detailed enough to guide selection.
Naming Consistency4/5
The openfinance_* prefix provides strong consistency for the bulk of tools, with clear verb_noun patterns (list, get, update, force_sync). The platform tools (authenticate, connect, marketplace, report_bug, etc.) break the pattern but are few and their names are intuitive. Overall, minor mixing of conventions but readable.
Tool Count4/5
25 tools is on the higher side but appropriate for a comprehensive Open Finance and platform management server. The count includes both data access (accounts, transactions, bills, loans, investments) and platform utilities (authentication, connection state, marketplace). No redundant tools; each serves a clear purpose.
Completeness4/5
The surface covers the core read operations for connected banks (accounts, transactions, bills, loans, investments), connection management (sync, status, disconnect), and category correction. Minor gaps include no get-transaction-by-id and no update for account metadata, but these are not critical for the typical use case of a banking data aggregator.