Wise MCP Server

List balances

list_balances

Read-onlyIdempotent

Retrieve a Wise profile's currency balances to view funds available for payments, amounts reserved, and optionally savings Jars.

Instructions

List the profile's currency balances: what is available to pay from, and what is reserved.

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_balances"
  }
}

Input Schema

Name	Required	Description	Default
`profile`	No	The Wise profile id to act for. Defaults to WISE_PROFILE_ID, else the only business profile. See list_profiles.
`include_jars`	No	Also list savings balances (Jars).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Nov 7, 2026

TDQS

A3.6/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, so the safety profile is covered. The description adds conceptual context about what a balance contains (available vs reserved), which is genuinely useful, but it omits whether Jars are excluded by default and says nothing about result shape or volume for a list operation with no output schema.

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 sentence that front-loads the action and resource, then spends one clause on the meaningful distinction between available and reserved funds. Nothing is wasted and nothing important is buried.

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 two-parameter, zero-required read tool with a fully documented schema and explicit read-only annotations, this covers most of what an agent needs. The only real gap is the default behavior for savings/Jars, which the schema mentions but the description does not reinforce, and the absent output schema means the brief return characterization must carry more weight.

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%, with both the profile default resolution and the include_jars meaning fully documented in the schema. The description adds no parameter-level detail beyond that, which is the expected baseline when the schema carries the full burden.

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 gives a specific verb ('List') plus the resource ('the profile's currency balances') and disambiguates the concept by defining balances as available-to-pay versus reserved. This separates it in spirit from get_balance or get_total_funds, though it never names those siblings, so an agent still has to infer which of the balance-related tools to pick.

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: the plural 'balances' suggests a full listing in contrast to the singular get_balance, but the description never states when to prefer this over get_balance, get_total_funds, or list_account_details_orders, nor any prerequisites beyond what the schema's profile parameter already says.

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