Wise MCP Server

Close or cancel a batch

update_batch

Destructive

Close a batch once all payments are in so it can be paid in Wise, or cancel the batch and all payments within it.

Instructions

Close a batch once every payment is in, so it can be paid in Wise (close), or cancel it and every payment in it (cancel). Closing does not pay it. A person approves either.

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": {
      "batch_id": "<batch_id>",
      "action": "<action>"
    },
    "name": "update_batch"
  }
}

Input Schema

Name	Required	Description
`action`	Yes	close: ready to pay in Wise. cancel: the batch and its payments are cancelled.
`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.
`batch_id`	Yes	The batch id.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Nov 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The annotations already flag destructiveHint=true, idempotentHint=false and openWorldHint=true, so the bar is lower; the description still adds real value by clarifying that close is non-paying and that a human approval step intervenes before either action takes effect. It does not mention irreversibility of cancel or what the call returns, leaving some behavioral detail to inference.

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?

Three short sentences, front-loaded with the primary outcome and immediately followed by the critical caveat that closing does not pay. Zero redundant wording.

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 4-parameter mutation with full schema coverage and no output schema, the description covers the action semantics, the human-approval gate, and the key consequence of cancel. A brief note on what state the batch is left in or what the response contains would close the remaining gap.

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%, including an enum with per-value documentation for 'action', so the baseline is 3. The description's explanation of close vs cancel largely restates what the enum description already says, adding no new syntax, format, or edge-case guidance for batch_id, profile, or confirm.

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 names both operations precisely (close a batch, cancel a batch and every payment in it) and explicitly disambiguates the most likely misconception — that closing pays the batch. This is a specific verb+resource statement that an agent can distinguish from create_batch or get_batch without opening a schema.

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?

It gives a clear condition for choosing close ('once every payment is in') and states the alternative behavior of cancel, plus the prerequisite that a person approves either action. It stops short of naming sibling tools or stating when not to use this tool at all, so it is clear context without explicit exclusions.

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