Skip to main content
Glama

Spend authority

spend_authority
Read-onlyIdempotent

Read an Arc Mandate box rules and check whether a payee and optional USDC amount are allowed right now. $0.005 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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": {
      "box": "<box>",
      "payee": "<payee>"
    },
    "name": "spend_authority"
  }
}

Input Schema

NameRequiredDescriptionDefault
boxYesMandate box address on Arc (0x...)
payeeYesseller address (0x...)
amountNooptional USDC amount to check
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: pricing ($0.005 per call), accepted payment rails (x402 with USDC on Arc/Base/Solana or XNT on X1), and the fact that passing `payment` completes the purchase inside the call. That last point sits in mild tension with readOnlyHint=true, since funds move, but the description surfaces it rather than hiding it, and the mandate box itself is not mutated. Minor remaining gaps are timeout/expiry behavior of the signed terms.

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?

Three sentences, front-loaded with the purpose before cost and protocol detail. The payment-rail parenthetical is dense but carries decision-relevant information. No filler sentences.

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 paid, open-world read tool with no output schema, the definition covers what it evaluates, how it is paid for, and how the payment handshake works. The one thing left implicit is the shape of the answer (allowed/denied plus reason), which an agent must discover from the call itself.

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 the baseline is 3, but the description genuinely adds semantics the schema lacks: `payment` operates in a challenge-then-sign-then-retry loop tied to the terms returned by the un-paid call. `amount` being optional for a payee-only check is reinforced by 'optional USDC amount'.

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?

Names a specific verb and resource: reads an Arc Mandate box's rules and evaluates whether a given payee (and optional USDC amount) is currently permitted. That is distinct from a generic allowance or balance check, so an agent can tell what it returns 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 Guidelines4/5

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

Gives an explicit two-step procedure: call once without `payment` to get the terms, sign them with your own wallet, call again with `payment`. That resolves the main usage ambiguity (which mode to call). It does not, however, say when to choose this over a nearby allowance/check tool or what to do when the check returns a denial.

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