Skip to main content
Glama

List transfers

wise_list_transfers
Read-only

List a Wise profile's transfers oldest first, with optional filters for status, source or target currency, and creation date range. Use createdDateStart to find recent transfers reliably.

Instructions

List transfers for a profile, OLDEST first, optionally filtered by status, currency and creation date. For recent transfers set createdDateStart rather than relying on order.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
statusNoComma-separated, e.g. incoming_payment_waiting,processing,outgoing_payment_sent,cancelled
profileIdNoWise profile ID. Optional when WISE_PROFILE_ID is set; get it from wise_list_profiles.
createdDateEndNoISO 8601 date, inclusive
sourceCurrencyNoSource currency (ISO 4217, e.g. EUR)
targetCurrencyNoTarget currency (ISO 4217, e.g. EUR)
createdDateStartNoISO 8601 date, inclusive

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds a genuinely non-obvious behavioral trait – results are returned OLDEST first, which surprises agents expecting recency ordering – plus the mitigation. It omits pagination behavior and result-set size limits, which the schema only implies.

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?

Two sentences, no filler, with the most consequential fact (ordering direction) placed before the optional-filter list. The mitigation advice follows immediately, so the reader never has to scan back.

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 an 8-parameter list tool with no output schema, the definition leaves the agent without any picture of a transfer record's shape, whether a total count is returned, or how limit/offset interact with the fixed oldest-first ordering. Annotations and the rich schema cover safety and filtering, so the gap is moderate rather than severe.

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?

With 75% schema description coverage, the schema already documents status, profileId, both date bounds and both currencies. The description adds only that the three filter dimensions are optional and the createdDateStart advice, leaving limit/offset semantics and the comma-separated status list to the schema. Baseline 3 is appropriate given the schema does most of the work.

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?

States a specific verb and resource ('List transfers') plus scope ('for a profile') and an explicit ordering rule ('OLDEST first'), which an agent can distinguish from wise_get_transfer by name alone. It does not explicitly contrast itself with sibling list tools such as wise_list_activities, so it stops short of full sibling differentiation.

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?

Offers one concrete usage directive: 'For recent transfers set createdDateStart rather than relying on order' – a real, actionable workaround for the oldest-first ordering. However, it gives no guidance on when to choose this tool over wise_get_transfer for a single record, nor any exclusion or prerequisite conditions.

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