Wise MCP Server

Open a currency balance

open_balance

Create a currency balance or named Jar to set aside savings without moving money. Specify a currency; add a jar name to make it a savings balance.

Instructions

Open a balance in a currency, or a Jar (a savings balance with a name) to set money aside. Opening one moves no money.

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": "open_balance"
  }
}

Input Schema

Name	Required	Description
`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.
`jar_name`	No	Make it a Jar (savings) with this name. Without it, a standard balance, one per currency.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Nov 7, 2026

TDQS

A3.8/5.0

Behavior3/5

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

The annotations already declare that this is not read-only, is open-world, is not idempotent, and is not destructive. The description adds a useful behavioral detail, that opening a balance moves no money, but it does not cover return behavior, duplicate handling, or permission requirements beyond what the schema and annotations already indicate.

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 two short sentences with no wasted wording. The key purpose and the no-money-movement behavior are front-loaded and easy to scan.

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 simple creation tool with rich parameter descriptions and clear annotations, the description covers the essential purpose and financial effect. It could be slightly more complete by mentioning what is returned or referencing duplicate-balance behavior, but the schema already notes the one-per-currency constraint.

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?

With 100% schema description coverage, the schema already explains the profile, currency, and jar_name parameters in detail. The description’s explanation of a Jar as a named savings balance aligns with the schema but does not add substantial new parameter semantics beyond it.

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 gives a specific verb and resource: open a balance in a currency or a Jar. It also clarifies the effect of the operation with 'Opening one moves no money,' which distinguishes it from money-moving operations such as transfers or deposits.

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 description implies when to use the tool by explaining that a Jar is for setting money aside, but it does not explicitly state when to choose this over alternatives or when not to use it. The usage context is present but not fully developed.

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