Skip to main content
Glama

Sending to bank accounts

get_payout_options
Read-onlyIdempotent

Lists where money can be sent to a bank account: the country, the currency it arrives in, the method, the fee, the largest amount and how fast it arrives, for personal and business accounts. Give a country, a currency or both. Use it when someone asks whether they can send money to a country, what it costs or how long it takes.

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

Input Schema

NameRequiredDescriptionDefault
countryNo
currencyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and a closed-world scope, so the safety profile is covered. The description adds real value beyond that: it says both filters are optional and combinable, and that results cover both personal and business accounts, which tells the agent what breadth of data to expect.

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, both dense with useful content: the first defines output shape, the second defines input flexibility and trigger conditions. Nothing is redundant and the core purpose is front-loaded.

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 two-optional-parameter lookup with no output schema, the description covers what the tool returns, when to reach for it, and that filtering is optional. The only real omission is input format for the country/currency codes, which matters given zero schema descriptions.

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 coverage is 0%, so the description carries the burden for both parameters, and it does clarify they are optional and can be supplied individually or together. However, it never states the expected formats (ISO-2 country code, ISO-3 currency), which is exactly the information the undocumented schema patterns require an agent to discover.

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 ('Lists where money can be sent to a bank account') and enumerates the returned attributes (country, currency, method, fee, max amount, speed, account types), which clearly separates it from a quote or rate tool. It never names a sibling such as get_send_quote or get_receiving_accounts to draw the boundary explicitly, so it falls short of a 5.

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?

It gives concrete triggering questions ('whether they can send money to a country, what it costs or how long it takes'), which is strong when-to-use guidance. It does not state when not to use it or which sibling to pick for an actual transfer quote, leaving that inference to the agent.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.