Skip to main content
Glama

agent-exec

Broadcast a USDC approval you signed, with our gas (paid, x402)

relay_permit

PAID: approve a USDC spender without gas: you sign an EIP-2612 Permit, we broadcast it on Base. $0.0200 an approval, at most $100. Unpaid, it returns the price; pay with x402 (USDC on Base, Solana, Polygon, Arbitrum, Avalanche, Sei or X Layer) in _meta['x402/payment'] and call again. Feedback: POST /feedback (free). Read daily; no individual reply.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "relay_permit"
  }
}

Input Schema

NameRequiredDescriptionDefault
nonceNoThe owner's current USDC nonces(owner), as a decimal string.
ownerNoThe USDC holder who signed, e.g. 0x2222222222222222222222222222222222222222. Needs no ETH.
valueNoAtomic USDC (6 decimals) as a decimal string, 0..100000000 ($100 ceiling). 0 revokes.
spenderNoThe contract or wallet approved to pull USDC. Must differ from owner.
deadlineNoUnix seconds, as a string; at least 30s out.
signatureNoYour EIP-712 Permit signature over chainId 8453, verifyingContract 0x833589fcd6edb6e08f4c7c32d4f71b54bda02913 (Base USDC).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false and openWorldHint=false; the description adds the material facts: it is paid ($0.0200 per approval, $100 ceiling), the accepted payment chains, and the exact unpaid-call behavior. It still omits what a successful paid call returns (e.g. a tx hash) and whether a spent nonce triggers a distinct error. Note that granting a spendable allowance is capability delegation even though destructiveHint is false, but the $100 cap and the '0 revokes' escape hatch in the schema make this a design choice rather than an outright contradiction.

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?

Pricing and the paid/unpaid mechanics are front-loaded and dense with no wasted phrasing. The trailing 'Feedback: POST /feedback (free). Read daily; no individual reply' is operator meta-commentary that does not help an agent invoke this tool and slightly dilutes the focus.

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 six-parameter, fully documented paid mutation with no output schema, the description covers cost, payment channel, chain, and the unpaid-call handshake. The remaining gap is the success-side contract: what the response contains and how nonce staleness or replay is reported is left unstated.

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 100%, so every parameter already carries its own explanation, including the chainId 8453 and Base USDC verifyingContract. The description adds only the framing that the signature is an EIP-2612 Permit and that the server broadcasts it. With the schema doing the heavy lifting, the baseline 3 applies.

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: it broadcasts an EIP-2612 Permit granting a USDC allowance on Base, and pays the gas itself. Contrast with the sibling relay_usdc is implicit but real, since this is explicitly the permit/approval path rather than a transfer, so an agent can route between them from the description alone.

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 a concrete call protocol: an unpaid call returns the price, then you put USDC payment in _meta['x402/payment'] and call again. That is enough for an agent to sequence the calls correctly. It does not state when to prefer this over sibling tools such as relay_usdc or execute, so it stops short of full when/when-not guidance.

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.