Skip to main content
Glama

List recipients

wise_list_recipients
Read-only

Retrieve saved recipient accounts with pagination using seekPosition from the prior response; filter by currency and profile to manage Wise transfer recipients.

Instructions

List saved recipient accounts. Paginate with seekPosition from the previous response's seekPositionForNext.

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_recipients"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNo
currencyNoFilter by target currency (ISO 4217, e.g. EUR)
profileIdNoWise profile ID. Optional when WISE_PROFILE_ID is set; get it from wise_list_profiles.
seekPositionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/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 safety is covered. The description adds real behavioral context the annotations cannot: that results are paged and that the continuation token is named seekPositionForNext in the response, which is non-obvious since there is no output schema. It omits any note on page-size defaults 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?

Two sentences, zero filler, with the identification of the tool front-loaded and the pagination mechanic immediately after. Nothing could be removed without losing information.

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 read-only list tool with four optional parameters and no output schema, the definition covers the essentials: what is returned, how to page, and where the token comes from. A brief note on ordering or what happens when currency/profile filters are omitted would make it fully self-sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%, and the description compensates for the most ambiguous gap: seekPosition is an opaque integer in the schema, but the description explains it must be sourced from the previous response's seekPositionForNext. Combined with the schema's own documentation of currency and profileId, the parameter picture is effectively complete.

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 opens with a specific verb and resource: 'List saved recipient accounts,' which tells an agent exactly what comes back (a collection of recipients). It stops short of differentiating itself from the sibling wise_get_recipient or wise_get_recipient_requirements, so the agent must infer that this is the collection-level read.

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?

The second sentence gives concrete procedural guidance for pagination, telling the agent to feed seekPosition from the prior response's seekPositionForNext. However, it never states when to prefer this over wise_get_recipient or wise_get_recipient_requirements, nor when a currency filter is appropriate; usage is implied rather than routed.

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