Wise MCP Server

wise_get_account_requirements

Read-only

Retrieve required bank-account fields for creating a recipient based on source and target currencies and amount. Fields differ by destination country.

Instructions

Get the required bank-account fields for creating a recipient in a given source→target currency + amount. Fields differ by country: USD routing number, EUR IBAN, GBP sort code, etc.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "source": "<source>",
      "target": "<target>",
      "sourceAmount": "<sourceAmount>"
    },
    "name": "wise_get_account_requirements"
  }
}

Input Schema

Name	Required	Description
`source`	Yes	Source currency code (ISO-4217)
`target`	Yes	Target currency code (ISO-4217)
`sourceAmount`	Yes	Source amount (influences which requirement fields are needed)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.7Jun 26, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations declare readOnlyHint and openWorldHint, which the description complements by explaining that fields differ by country (e.g., USD routing number, EUR IBAN). This adds behavioral context beyond the annotations without 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?

The description is extremely concise: a single focused sentence with an informative example. Every word adds value, and the core action is front-loaded.

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 full schema coverage, readOnlyHint, openWorldHint, and no output schema, the description is complete for its purpose. It explains what is returned and why, though could mention it's a read operation explicitly (but annotations cover that).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with adequate parameter descriptions. The description reiterates the source→target currency+amount context but does not add new meaning beyond the schema. Score at baseline 3 as schema already handles parameter semantics.

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 tool retrieves required bank-account fields for creating a recipient based on source/target currency and amount. It distinguishes itself from sibling tools by focusing on account requirements, not balances or transfers.

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 when to use the tool (when creating a recipient and needing required fields), but it does not provide explicit guidance on when not to use it or mention alternatives. The sibling list is provided, which helps context but lacks direct exclusions.

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

Deploy Server