Skip to main content
Glama

Get transactions to pay an invoice

get_payment_transactions
Read-only

Returns unsigned token approval (if needed) and invoice payment transactions for the payer to review and sign in their own wallet.

Instructions

For the PAYER: returns the unsigned transaction(s) needed to pay an invoice (a token approval, if needed, then the payment). This server never signs or sends anything; the payer reviews and signs them in their own wallet.

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": {
      "requestId": "<requestId>"
    },
    "name": "get_payment_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestIdYes
payerWalletNoPayer wallet, used to check balance and approval.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

The description explains the crucial behavior behind readOnlyHint=true: the server never signs or sends anything, and the payer signs in their own wallet. It also discloses that the result may be a multi-step sequence (approval, if needed, then payment), which annotations cannot convey. It stops short of stating whether the returned calldata is cached, expiring, or chain-specific.

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 tightly written sentences, front-loaded with the audience marker 'For the PAYER' followed by the return content, then the safety constraint. Nothing is redundant and no sentence could be dropped 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?

With only two parameters and no output schema, the description must convey the return value itself, and it does: unsigned transaction(s), possibly an approval plus a payment. It leaves the concrete shape (array vs. object, chain/from/to fields) unspecified, which an agent must discover at runtime, but the semantic content an agent needs to plan the call is present.

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 50%: payerWallet is documented in the schema, while requestId carries only a regex pattern with no meaning. The description's mention of a token approval 'if needed' hints that approval/balance checking relates to the payer wallet, but it never clarifies what requestId identifies or why payerWallet is optional. Baseline 3 is appropriate given the partial coverage.

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?

The description names a specific verb and resource — 'returns the unsigned transaction(s) needed to pay an invoice' — and scopes it to the PAYER, with the returned sequence (approval then payment) spelled out. No sibling (create_invoice, check_invoice, list_invoices, create_payment_link, find_currency) produces unsigned calldata, so the tool is distinguishable without opening the schema.

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?

'For the PAYER' implies the usage context (a payer settling an existing invoice), but there is no explicit when-to-use or when-not-to-use guidance and no named alternatives such as check_invoice for verifying the invoice first. Usage is inferable rather than stated.

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