Wise MCP Server

How much a balance can hold

get_deposit_limit

Read-onlyIdempotent

Check whether a Wise currency balance has a deposit limit for a profile and retrieve the limit amount.

Instructions

Whether a currency balance has a deposit limit where the profile is based, and how much it is.

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

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.
`currency`	Yes	The currency, such as EUR.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Nov 7, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description goes beyond them by disclosing that the answer is jurisdiction-dependent (based on the profile's location) and that the result has two parts – a has-limit boolean plus the amount – which matters since no output schema exists.

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?

A single front-loaded sentence with no filler, but the phrasing is slightly convoluted ('Whether a currency balance has a deposit limit where the profile is based, and how much it is') rather than plainly stating verb and return shape.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool this is close to adequate, but with no output schema the description should say what comes back when no limit applies (e.g. null or omitted) and what currency/amount units mean. Those gaps leave the agent guessing about the response shape.

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 both parameters are already documented in the input schema with defaults and format patterns. The description adds only that the profile's location determines the limit, which is mild meaning beyond the schema; baseline 3 applies.

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 the specific resource (a currency balance's deposit limit) and states the two things it answers: whether a limit exists and what it is. It also notes the jurisdiction qualifier ('where the profile is based'), which separates it from generic balance queries, though it never names a sibling tool to contrast against.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no prerequisite or sequencing advice (e.g. call before open_balance or create_transfer), and no alternatives named among the many sibling tools. Usage is only inferable from the phrase 'deposit limit'.

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