Wise MCP Server

A batch

get_batch

Read-onlyIdempotent

Retrieve a Wise batch's status and payments, plus payment instructions once the batch is closed.

Instructions

A batch's status, its payments, and, once closed, how to pay 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": {
      "batch_id": "<batch_id>"
    },
    "name": "get_batch"
  }
}

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.
`batch_id`	Yes	The batch id, from create_batch.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Nov 7, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds one genuine behavioral fact beyond that: payment instructions are only returned after the batch is closed, which explains a state-dependent result shape. It says nothing about authorization, rate limits, or behavior for open batches.

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 compact clause with no filler; the most important content (status and payments) comes first. It is arguably over-compressed into a sentence fragment, but nothing in it is wasted.

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 simple read tool with full schema coverage and rich annotations and no output schema, the description covers the essentials of what is returned. It stops short of describing the shape of the payments list or how the agent should interpret an open versus closed batch, leaving moderate gaps.

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% and both parameters (batch_id, profile) are documented in the schema, including the WISE_PROFILE_ID default and the pointer to list_profiles. The description contributes no additional meaning about parameter usage, so the baseline of 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 resource (a batch) and enumerates what is retrieved: status, payments, and payment instructions once closed. That is concrete enough to separate it from create_batch/update_batch/list_transfers, though it omits an explicit verb ('retrieve') and relies on an elliptical noun phrase.

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 statement of when to call this versus siblings such as create_batch, update_batch, or list_transfer_payments. The only implied routing signal is the 'once closed' condition about payment instructions, which tells the agent nothing about choosing this tool.

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