Skip to main content
Glama

pay_work_ticket_quote

Pay the buyer-accepted quote directly to the seller with x402 Base USDC. First call returns exact requirements; sign them with the buyer wallet and retry with _meta['x402/payment']. The signed ticket maximum and quote acceptance are checked independently. Keep idempotencyKey and the same payment authorization for recovery.

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": {
      "ticketId": "<ticketId>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "pay_work_ticket_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
ticketIdYes
idempotencyKeyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses an on-chain USDC payment, a challenge/retry handshake, and two independent validations (signed ticket maximum and quote acceptance). It leaves out failure modes and whether the transfer is irreversible, which matters for a funds-moving tool.

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?

Four tight sentences with the payment action front-loaded, followed by the call sequence and recovery advice. Dense protocol jargon ('x402/payment') is unavoidable but slightly reduces first-read clarity.

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-parameter, no-output-schema payment tool with no annotations, the description covers the mechanism, the handshake, validation, and recovery adequately. The notable gap is that it references a payment payload property the schema forbids, which an agent could trip over.

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 description coverage is 0%, so the description must compensate for both parameters. It adds real meaning for idempotencyKey ('keep ... for recovery') but never explains ticketId beyond the implied work ticket, nor the key's format constraints; the _meta['x402/payment'] field it instructs callers to send is absent from a schema that sets additionalProperties=false.

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 gives a specific verb and resource ('Pay the buyer-accepted quote directly to the seller') plus the settlement mechanism ('x402 Base USDC'), which is enough to separate it from accept_work_ticket_quote and quote_work_ticket. It stops short of naming the sibling it must follow, so the differentiation is inferred rather than stated.

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 clearly describes the two-step invocation flow: the first call returns requirements, the caller signs with the buyer wallet, then retries with _meta['x402/payment']. It also prescribes recovery behavior ('Keep idempotencyKey and the same payment authorization'). It does not state preconditions such as 'only after the quote is accepted' or what to do if signing fails, so exclusions are missing.

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