show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Inter MCP
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4.3/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds no further behavioral traits beyond specifying the versions returned. No contradiction.
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 sentence, no wasted words, clearly communicates purpose.
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 info tool with no output schema, the description is complete and sufficient.
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, so description does not need to add param info. Baseline 4 per schema coverage rules.
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?
Description uses specific verb 'Show' and resource 'current MCP platform and adapter versions'. Clearly distinguishes from sibling tools which handle authentication, financial data, etc.
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?
No explicit when-to-use or alternatives, but the tool's function is self-evident and simple. Context implies use when version info is needed.
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
Disambiguation5/5
Each tool targets a distinct resource or action: the openfinance_* family cleanly separates accounts, transactions, bills, loans, investments, connections, sync, and provider health, while platform tools (authenticate, connect, marketplace, toolkit_info) cover different concerns. Even potentially similar pairs like get_item_status vs provider_status and list_transactions vs list_transactions_by_item are clearly differentiated by their descriptions.
Naming Consistency4/5
Open Finance tools follow a uniform openfinance_<verb>_<noun> snake_case pattern, and the generic tools are also readable English verbs/nouns (authenticate, connect, report_bug). The main inconsistency is that a few generic tools are bare nouns (marketplace, toolkit_info) while the rest are verbs, but the mix is predictable and never confusing.
Tool Count3/5
25 tools sit at the upper boundary of what is comfortable, and the set spans two distinct domains (Open Finance data access plus MCP platform/marketplace management). Each tool does appear to earn its place, but the count is heavy enough to feel borderline rather than optimally scoped.
Completeness5/5
The Open Finance surface is thorough: list/get for accounts, transactions, bills, loans, and investments, with sync, connection health, provider status, category correction, and disconnect all covered. The platform side also covers authentication, connection status, marketplace discovery/invocation, bug reporting, and version info, leaving no obvious dead ends for the stated purpose.