show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Stone Pagamentos 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 provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false, establishing a safe read-only behavior. The description adds the nuance of 'current' versions, indicating the output may change over time, which is useful beyond the 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?
The description is a single, concise sentence that directly states the tool's function. It contains no unnecessary words or repetition, earning a perfect score for conciseness.
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, parameterless version-information tool with comprehensive annotations, the description is fully adequate. It clearly conveys what information will be presented, and the lack of output schema is not a gap given the trivial nature of the response.
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 description appropriately does not attempt to describe nonexistent parameters. Per the rubric, a baseline of 4 is applied when there are no parameters.
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 resource 'MCP platform and adapter versions', clearly stating what the tool does. It distinguishes itself from siblings like toolkit_info by focusing specifically on version display.
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 usage when version information is needed for debugging or compatibility checks. It provides clear context without explicit exclusions, and there are no conflicting sibling tools that also fetch versions.
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
Most tools have clearly distinct purposes, especially within the openfinance_* group (list vs get vs sync vs status). A few potential overlaps exist (e.g., openfinance_list_transactions vs openfinance_list_transactions_by_item, openfinance_get_account_balance vs openfinance_list_accounts), but descriptions are detailed enough to guide correct selection.
Naming Consistency4/5
The openfinance_* tools follow a consistent verb_noun pattern (e.g., openfinance_list_accounts, openfinance_get_item_status). However, non-openfinance tools (authenticate, connect, marketplace, toolkit_info) use a different style, and one tool (openfinance_list_transactions_by_item) breaks the pattern slightly. Overall readable and predictable within the primary domain.
Tool Count3/5
With 25 tools, the count is on the heavy side per the calibration rubric (16-25 feels heavy). The server covers a broad financial data domain, which justifies the number, but it may present a steep learning curve and potential overwhelm for agents.
Completeness4/5
The tool surface is comprehensive for read-only Open Finance data access: accounts, transactions, balances, bills, loans, investments, category management, connection lifecycle, and status monitoring. Minor gaps exist (e.g., no direct payment initiation, no investment transaction creation), but for the stated purpose of data and analysis, coverage is strong.