Wise MCP Server

Order local bank details

order_account_details

Destructive

Order local bank details for a currency, such as a USD account and routing number, so others can pay your Wise profile; Wise may require extra information and a person must approve.

Instructions

Order local bank details for a currency, such as a USD account and routing number, so others can pay the profile in it. Wise may ask for more before issuing them. A person approves it.

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": {
      "currency": "<currency>"
    },
    "name": "order_account_details"
  }
}

Input Schema

Name	Required	Description
`confirm`	No	Set true only when the user asked for exactly this action.
`profile`	No	The Wise profile id to act for. Defaults to WISE_PROFILE_ID, else the only business profile. See list_profiles.
`currency`	Yes	The currency, such as USD or GBP.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Nov 7, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already flag the operation as destructive, open-world, and non-idempotent. The description adds non-obvious behavioral context—'Wise may ask for more before issuing them' and 'A person approves it'—which tells the agent that issuance is conditional and requires human approval. It does not detail irreversible consequences, but with annotations covering the safety profile this is a strong addition.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is front-loaded with purpose and kept to three short sentences. Each sentence adds value, though the final sentence 'A person approves it' is slightly abrupt and could be integrated more smoothly without losing clarity.

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 moderately complex mutation tool without an output schema, the description covers what the tool does, the conditional nature of issuance, and the human approval requirement. It leaves some operational details (e.g., cost or how to check order status) to sibling tools like list_account_details_orders, but overall it is sufficient for correct invocation.

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 description coverage is 100%, so the schema already documents all three parameters thoroughly. The description mentions 'for a currency' and 'the profile' but adds no meaning beyond the schema, such as how confirm interacts with human approval. Baseline 3 is appropriate.

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 states a specific verb (Order) and resource (local bank details) for a currency, with a concrete example. It clearly conveys what the tool does, though it does not explicitly differentiate itself from siblings like list_account_details_orders or check_bank_details.

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?

The phrase 'so others can pay the profile in it' implies the use case of enabling incoming payments, but there is no explicit when-to-use guidance or mention of alternatives or prerequisites. The agent must infer the appropriate context from the purpose statement.

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