Skip to main content
Glama

Get recipient requirements

wise_get_recipient_requirements
Read-only

Lists recipient account types and exact fields required for a quote so you can prepare a recipient before creating it.

Instructions

For a quote, list which recipient account types exist for the route (e.g. iban, sort_code, aba) and the exact fields each needs. Call this before wise_create_recipient.

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": {
      "quoteId": "<quoteId>"
    },
    "name": "wise_get_recipient_requirements"
  }
}

Input Schema

NameRequiredDescriptionDefault
quoteIdYesQuote ID from wise_create_quote

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered structurally. The description adds real value beyond that by explaining that results are route-dependent (derived from the quote) and by describing what the response conceptually contains, which matters since there is no output schema. It does not mention failure behavior for unsupported routes, keeping it below the top score.

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 tight sentences: the first explains what is returned, the second gives the call-order directive. Nothing is redundant and the prerequisite is placed where it will be read.

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 single-parameter read tool with no output schema, the description covers the essentials: input dependency, output content, and workflow placement. Minor gaps remain around behavior on unsupported routes or how the field list is structured, but nothing critical is missing for correct invocation.

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

Parameters4/5

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

Schema coverage is 100% and quoteId is already documented as coming from wise_create_quote. The description adds meaning by tying the parameter to a route concept — the quote determines which account types and fields apply — which the schema alone does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: lists recipient account types for a given quote's route (with concrete examples iban, sort_code, aba) plus the exact fields each type requires. That is clearly distinct from wise_get_recipient and wise_list_recipients, which deal with existing recipients rather than route requirements.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit sequencing guidance: 'Call this before wise_create_recipient.' That tells the agent exactly where this fits in the workflow. It stops short of stating when not to call it (e.g. that it is unnecessary once requirements are already known), so it is strong but not exhaustive.

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