Wise MCP Server

Currencies Wise supports

list_currencies

Read-onlyIdempotent

Fetch the currencies Wise can send to, including symbol, name, and decimal support, so you can validate payout options or format amounts correctly.

Instructions

Every currency Wise can send to, with its symbol, name and whether it has decimals.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_currencies"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Nov 7, 2026

TDQS

A3.9/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), so the bar is lower. The description still adds real value by disclosing the payload fields returned (symbol, name, decimal flag), which matters because no output schema exists. It does not state whether the list is paginated or cached, a minor gap for a small fixed list.

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?

A single front-loaded sentence with no filler; the scope (all sendable currencies) comes first and the returned fields follow, so every clause 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?

For a zero-parameter, read-only enumeration, the definition plus annotations give an agent everything needed to call it and to know roughly what comes back. The only missing piece is return-shape detail such as ordering or size, which is minor here.

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 takes no parameters, so the baseline is 4. The description correctly implies no input is needed by framing the call as a plain enumeration.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource and scope: 'Every currency Wise can send to', which tells an agent this is a full enumeration of sendable currencies rather than a rate lookup. It is clearly separable from siblings like get_rate and compare_prices, though it never uses an explicit listing verb.

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?

Usage is only implied — an agent can infer this is the tool to call to discover supported currencies (e.g. before create_quote or create_transfer). There is no explicit statement of when to prefer this over get_rate or compare_prices, and no exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.