Skip to main content
Glama

Get transfer

wise_get_transfer
Read-only

Retrieve a transfer's details and current status by transfer ID so agents can track its progress and confirm its payout state.

Instructions

Get a transfer's details and current status.

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": {
      "transferId": "<transferId>"
    },
    "name": "wise_get_transfer"
  }
}

Input Schema

NameRequiredDescriptionDefault
transferIdYesTransfer ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/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 and the fact that this is an external live lookup are covered structurally. The description adds only that the returned status is 'current', implying a fresh fetch rather than a cached record; it says nothing about failure modes for unknown IDs or rate limits.

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?

One sentence, front-loaded with the verb and resource, and every word earns its place. Nothing redundant or padded.

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 single-parameter read tool with annotations covering safety and no output schema, the definition is sufficient to call it. However, with no output schema, a brief indication of what 'details' comprise (amount, target currency, recipient, state) would help the agent decide whether this call answers its question.

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 the single parameter (transferId, positive integer) is fully documented in the schema. The description adds no format, sourcing, or validity meaning beyond that, which is the expected baseline when the schema does 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?

The description states a specific verb (get) and resource (a transfer), plus what it returns: details and current status. It is clear on its own, but it doesn't distinguish this from look-alike siblings such as wise_get_quote or wise_get_recipient, relying on the resource noun alone to separate them.

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 when-to-use guidance, no mention of prerequisites (e.g. needing a transferId from wise_list_transfers or a create call), and no alternatives named for retrieving transfer information. The agent must infer the calling context entirely from the single required parameter.

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