Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Payment plan: which rail to pay a verified payee on

payee_plan
Read-only

Plan a payment to a payee before paying it: from its verified record (company, sanctions, signed wallets) and the rails it accepts (x402 USDC, MPP, card checkout, SEPA Instant, Swish), the best rail for the amount and currency and exactly what to pay where, plus finality, chargebacks and how to get a receipt. Never pays, routes or holds money. Use before paying when the buyer can pay several ways. Example: domain=agent-data-tools.revmesh2074.workers.dev. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": {
      "domain": "<domain>"
    },
    "name": "payee_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
canNoRails the buyer can pay on, comma-separated: x402, mpp, card, sepa-instant, swish (default all)
amountNoAmount to pay, in currency (optional; used for rail minimums)
domainYesThe payee's domain, e.g. shop.example.com
networkNoOnly x402 rails on this network, e.g. base
currencyNoISO currency of the price: USD (default), EUR, SEK… USDC counts as USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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, and the description consistently reinforces that with 'Reads or computes only and changes nothing' and 'Never pays, routes or holds money'. It goes further than the annotations by disclosing cost behavior ('each call is charged, so repeats are not free', 'failed calls free'), which is exactly the kind of non-idempotency/cost context the annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the purpose, then the constraint, then the return contents - a sound ordering for an agent scanning for fit. It is somewhat overloaded with colon-chained clauses and pricing/plan detail ('Price $0.01/call ... first 25 free') that reads partly as promotion, though the charged-per-call note does carry real behavioral value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must carry return-value burden, and it does: it names the plan result, the per-rail finality, chargebacks, and receipt path. Combined with read-only annotations and full schema coverage, an agent has everything needed to call it correctly and interpret the result.

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 100%, so domain, can, amount, network, and currency are already documented with examples and semantics. The description mostly restates the same rails and the same amount/currency relationship ('best rail for the amount and currency'), and its example domain duplicates the schema's own example. Baseline 3 is appropriate given the schema does the heavy lifting.

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: 'Plan a payment to a payee before paying it', and spells out the inputs consumed (verified record, accepted rails) and the output produced ('the best rail for the amount and currency and exactly what to pay where, plus finality, chargebacks and how to get a receipt'). This is clearly a planning/decision tool, distinguishable from verification siblings like check_payee or check_x402_seller.

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 an explicit trigger ('Use before paying when the buyer can pay several ways') and an explicit non-trigger ('Never pays, routes or holds money'), which tells the agent this is not the payment step. No sibling tool is named as an alternative and no exclusions against the verification tools are stated, so it stops short of a 5.

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.