Skip to main content
Glama

Validate LATAM payout beneficiary

validate_payout_beneficiary
Read-onlyIdempotent

Check a payout beneficiary's tax ID and bank account (or PIX key) for Mexico, Brazil, Argentina, Chile, Colombia or Uruguay before sending money. Validates format, check digits and bank code against central-bank directories. Returns verdict ready | review | invalid with error codes and bank name. MX: RFC + CLABE. BR: CPF/CNPJ + PIX key. AR: CUIT/CUIL + CBU/CVU. CL/CO/UY: tax ID + account with bank_code. Does not confirm account ownership.

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": {
      "country": "<country>"
    },
    "name": "validate_payout_beneficiary"
  }
}

Input Schema

NameRequiredDescriptionDefault
tax_idNoRFC (MX), CPF/CNPJ (BR), CUIT/CUIL (AR), RUT (CL), NIT (CO), RUT/CI (UY)
accountNoCLABE (MX), CBU/CVU (AR), or local account number (CL, CO, UY; needs bank_code)
countryYesISO country code of the beneficiary
pix_keyNoPIX key (BR only)
bank_codeNoCL: CMF code (012 BancoEstado). CO: CENIT code (1007 Bancolombia, 1507 Nequi). UY: BCU code (001 BROU, 113 Itau)
account_typeNoOptional; improves CO checks

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent and non-open-world, so the description correctly spends its words elsewhere: it discloses external validation against central-bank directories, the verdict taxonomy (ready | review | invalid) with error codes and bank name, and the ownership caveat. What it does not disclose is failure behavior for missing or malformed per-country inputs.

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?

Front-loaded purpose, then mechanism, then return values, then the country matrix, then the limitation. Dense but nothing is redundant; the compressed country lines are the most efficient encoding of the requirements.

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 6-parameter tool with no output schema, it covers purpose, per-country requirements, outcome values and a key limitation. It is silent on partial inputs (e.g. BR without pix_key) and on what a "review" verdict obliges the caller to do next.

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%, so 3 is the baseline; the description earns above that by expressing the cross-field conditional the per-field schema cannot: which identifiers pair with which country (MX: RFC + CLABE, BR: CPF/CNPJ + PIX, AR: CUIT/CUIL + CBU/CVU, CL/CO/UY: tax ID + account with bank_code).

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 (validate a payout beneficiary's tax ID and bank account / PIX key) and scopes it to six named LATAM countries and to the pre-transfer moment. The per-country document matrix makes the resource concrete and distinguishes it from a batch validator.

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?

Clearly signals when to use it ("before sending money") and adds an explicit exclusion ("Does not confirm account ownership"). It never names validate_payout_batch as the multi-beneficiary alternative, so routing for bulk checks is left to inference.

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.

Resources