show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Wise
TDQS
A4.2/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. The description adds no additional behavioral traits beyond confirming it shows versions. With annotations covering safety, this is adequate but not enhanced.
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 short sentence, directly front-loading the purpose. No extraneous information, every word earns its place.
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 no output schema and no parameters, the description covers the essential purpose. It could mention the format or typical use case, but overall it is complete for a simple version 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?
The tool has zero parameters, so the description does not need to add parameter info. Baseline is 4, and the description is sufficient.
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 verb 'show' and the resource 'current MCP platform and adapter versions', making the purpose obvious. It is distinct from sibling tools which involve authentication, connectivity, 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 implies usage for checking versions. No explicit when-not or alternatives are provided, but given the simplicity and read-only nature, the usage is clear and unlikely to be confused with other tools.
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.9/5.0
Disambiguation5/5
Every tool has a clearly distinct purpose. The six general MCP platform tools (authenticate, connect, marketplace, etc.) are separate from the six Wise-specific query tools (wise_get_balance_statement, wise_list_profiles, etc.). No two tools overlap in functionality.
Naming Consistency4/5
The Wise-specific tools consistently follow the pattern 'wise_verb_noun' (e.g., wise_get_balance_statement, wise_list_profiles). The general tools use short descriptive names without a prefix, which is a minor inconsistency, but the grouping is logical and readable.
Tool Count5/5
With 12 tools, the server is well-scoped. It provides sufficient coverage for both the MCP platform utilities and the Wise financial data integration without being bloated or sparse.
Completeness4/5
The tool set covers the core read operations for Wise (profiles, balances, transactions, card events, activities) and the essential MCP platform functions. Missing are write operations like creating transfers, but the server's focus appears to be data retrieval, so this is a minor gap.