Skip to main content
Glama

pay

Destructive

Reserves budget and signs a single x402 v2 exact USDT Permit2 challenge for an owner-approved resource; does not submit settlement, and signed authorizations hold capacity until settled or expired.

Instructions

Reserve budget and sign one x402 v2 exact USDT Permit2 challenge for an owner-approved resource. Does not submit settlement. Signed authorizations consume capacity until settled or expired.

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": {
      "resource": "<resource>",
      "challenge": "<challenge>"
    },
    "name": "pay"
  }
}

Input Schema

NameRequiredDescriptionDefault
resourceYes
challengeYes
operation_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already flag destructive=true, readOnly=false, openWorld=true and non-idempotent, so the safety profile is covered. The description adds genuinely new consequences: budget is reserved, settlement is not submitted, and signed authorizations consume capacity until settled or expired. It stops short of covering replay behavior or why operation_id exists despite a non-idempotent hint.

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?

Three short sentences with no filler: action first, the key exclusion second, the capacity consequence last. The jargon density is precision rather than padding, and nothing repeats the annotations or the schema.

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

Completeness3/5

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

For a destructive, open-world mutation with an opaque nested object and no output schema, the description covers side effects well but leaves the response undefined and the operation_id semantics unstated. An agent still cannot tell what it receives on success or how to retry safely. Adequate but with clear gaps for this complexity level.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, including a free-form nested 'challenge' object with additionalProperties, so the description must compensate and largely does not. It hints that 'challenge' is an x402 v2 exact USDT Permit2 challenge and that 'resource' is owner-approved, but never explains the required shape of the challenge or what operation_id is for. Half the parameter surface is undocumented everywhere.

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?

States a precise compound verb plus resource: 'Reserve budget and sign one x402 v2 exact USDT Permit2 challenge'. The qualifier 'Does not submit settlement' cleanly separates it from anything that actually settles payment. It never names a sibling (x402_fetch, transfer_usdt) as the alternative, so differentiation is inferable rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies a precondition ('for an owner-approved resource') but never says when to call this instead of x402_fetch or transfer_usdt, nor what happens when a resource is not owner-approved. 'Does not submit settlement' describes behavior, not a selection rule. An agent must guess the call ordering on its own.

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