Skip to main content
Glama

Get balance statement

wise_get_balance_statement
Read-only

Retrieve transactions for a single Wise balance within a specified time range, returning a statement for reconciliation or reporting. Requires SCA for UK/EEA profiles.

Instructions

Get the transactions on one balance between two times. Needs SCA (WISE_PRIVATE_KEY_PATH) for UK/EEA profiles; personal tokens only support this for US, CA, AU, NZ, SG and MY accounts.

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": {
      "balanceId": "<balanceId>",
      "currency": "<currency>",
      "intervalStart": "<intervalStart>",
      "intervalEnd": "<intervalEnd>"
    },
    "name": "wise_get_balance_statement"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoCOMPACT
currencyYesBalance currency (ISO 4217, e.g. EUR)
balanceIdYesBalance ID from wise_get_balances
profileIdNoWise profile ID. Optional when WISE_PROFILE_ID is set; get it from wise_list_profiles.
intervalEndYesUTC ISO 8601; max 469 days after start
intervalStartYesUTC ISO 8601, e.g. 2026-10-01T00:00:00.000Z

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds real behavioral context beyond that: an authentication dependency and token-type restrictions that determine whether the call will succeed at all. It stops short of describing return shape or pagination behavior for a statement covering up to 469 days.

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?

Two sentences, no filler, with the core operation stated first and the constraint second. The auth sentence is dense but every clause carries operational weight; a small deduction for packing several regional conditions into one unbroken sentence.

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?

Auth constraints are well covered, but with no output schema the description should at least signal what a statement returns and how COMPACT versus FLAT affects it. For a read tool with a potentially large time window and no result description, this leaves an agent uncertain about the response.

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 83%, so the schema already carries nearly all parameter meaning, including the balanceId linkage to wise_get_balances and the 469-day interval limit. The description adds nothing parameter-specific, in particular no explanation of the COMPACT vs FLAT enum, so the 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 gives a specific verb and resource ('Get the transactions on one balance') and scopes it in time ('between two times'), which is clearer than the title 'Get balance statement.' It does not explicitly contrast itself with wise_get_balances or wise_list_activities, but the singular 'one balance' scope distinguishes it well enough.

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?

It supplies hard preconditions for use (SCA via WISE_PRIVATE_KEY_PATH for UK/EEA; personal tokens limited to US, CA, AU, NZ, SG, MY), which is genuinely useful context. However, it never states when to prefer this over sibling reads like wise_get_balances or wise_list_activities, so the alternative-selection guidance is only implied.

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