show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Caixa Tem MCP
TDQS
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description carries a low burden. It adds context about the specific version information shown, but does not disclose additional behavioral traits beyond what annotations provide.
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. Every word adds value.
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 the tool has no parameters, no output schema, and strong annotations, the description is sufficient. It could briefly mention the return format (e.g., strings), but it's not necessary for correct usage.
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, and schema description coverage is 100%. The description need not add parameter information; the absence of parameters is well-handled.
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 clearly identifies the resources ('MCP platform and adapter versions'). It effectively distinguishes this tool from all siblings, none of which are version-related.
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 usage for checking versions, but does not provide explicit when-to-use or when-not-to-use guidance. No alternatives are mentioned, but given the uniqueness of this tool, the omission is minor.
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.8/5.0
Disambiguation3/5
The openfinance_* tools are mostly distinct, but several have overlapping boundaries: openfinance_list_transactions vs openfinance_list_transactions_by_item, openfinance_get_item_status vs openfinance_provider_status, and openfinance_list_accounts carrying balance vs openfinance_get_account_balance. The platform-level tools also blur somewhat: marketplace, toolkit_info, and connect all touch installed or available services.
Naming Consistency3/5
The openfinance_* group follows a consistent list/get/update verb pattern in snake_case, but platform-level tools like authenticate, connect, marketplace, report_bug, show_version, and toolkit_info break that convention. The set is readable, but it is split between two clearly different naming styles.
Tool Count3/5
At 25 tools, the server is at the heavy end, and several are platform/MCP-management helpers rather than core banking capabilities. The count is not absurd for a broad Open Finance + marketplace adapter, but it feels more cluttered than a focused financial data toolset should be.
Completeness4/5
The Open Finance surface is thorough: accounts, transactions, balances, credit card bills, loans, investments, connection lifecycle, sync, provider status, and category correction are all covered. The main gaps are the absence of a direct connect/create action (only URLs are returned) and no write operations beyond category updates, but for a read-centric financial data adapter this is close to complete.