Skip to main content
Glama

Agent Embassy

by pro.aemb
OverviewDiscussionsAdmin

Agent ID — Revoke

agentid_revoke
DestructiveIdempotent

Use agentid_revoke to retire an Agent ID instantly. revocation_signature: hex signature over the message agent-id-revoke:<agent_id> (64-char lowercase ID). EIP-191: personal_sign the message string (envelope required; raw ECDSA fails), 0x 65-byte hex, matched to the principal's revocation key. ed25519: nacl.sign.detached, 64-byte hex. Signer: principal or Embassy-for-cause. POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header. See https://docs.cdp.coinbase.com/x402 Paid tool — $0.25, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/agent-id/revoke.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonYesWhy the Agent ID is being retired (required, max 500 characters)
agent_idYesThe Agent ID string returned at issuance (64 hex characters; case-insensitive). Unknown IDs are rejected
idempotency_keyNoOptional idempotency key: UUID v4 (client-generated; published example keys are rejected). When provided, replaying the same key returns the original receipt instead of re-running the action; when omitted, no dedupe occurs. Keys are scoped per tool and per payer account: the same key on another tool — or from another wallet — is unrelated.
revocation_signatureYesHex signature over the exact UTF-8 message agent-id-revoke:<agent_id> (64-char lowercase ID, no trailing newline). EIP-191: personal_sign the message STRING (personal_sign envelope REQUIRED — raw ECDSA will not verify), 0x 65-byte hex r||s||v (v=27/28). ed25519: nacl.sign.detached over the message bytes, 64-byte hex. Signer: the principal's on-file revocation key, or the Embassy signer for cause

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
howYesHow to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
toolYesTool name, e.g. ping
assetYesSettlement asset
priceYesExact price, e.g. "$0.05"
networksYesEVM CAIP-2 network ids accepted
paid_urlYesx402-paid HTTPS URL to POST the tool inputs to
facilitatorYesx402 facilitator
payment_requiredYesAlways true: this MCP tool is a payment pointer; the tool itself is monetized via x402.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / price / description
      Previous value: -"Exact price, e.g. \"$0.15\""New value: +"Exact price, e.g. \"$0.05\""
  2. Changed1 schema field changed
    • changedOutput schema / properties / tool / description
      Previous value: -"Tool name, e.g. verified_check"New value: +"Tool name, e.g. ping"
  3. Changed2 schema fields changed
    • removedInput schema / properties / agent_wallet
      Removed value: -{
-  "description": "Dev mode only: declares the account wallet (string, min 20 chars) when no x402 payment is present. Ignored in live mode — there the wallet is recovered from the verified payment authorization.",
-  "type": "string"
-}
    • changedInput schema / properties / idempotency_key / description
      Previous value: -"Optional idempotency key: any non-empty string (a UUID is recommended; no format is enforced). When provided, replaying the same key returns the original receipt instead of re-running the action; when omitted, no dedupe occurs. Keys are scoped per tool: the same key on another tool is unrelated."New value: +"Optional idempotency key: UUID v4 (client-generated; published example keys are rejected). When provided, replaying the same key returns the original receipt instead of re-running the action; when omitted, no dedupe occurs. Keys are scoped per tool and per payer account: the same key on another tool — or from another wallet — is unrelated."
  4. Changed5 schema fields changed
    • addedInput schema / properties / agent_id / description
      Added value: +"The Agent ID string returned at issuance (64 hex characters; case-insensitive). Unknown IDs are rejected"
    • changedInput schema / properties / agent_wallet / description
      Previous value: -"dev mode only"New value: +"Dev mode only: declares the account wallet (string, min 20 chars) when no x402 payment is present. Ignored in live mode — there the wallet is recovered from the verified payment authorization."
    • addedInput schema / properties / idempotency_key / description
      Added value: +"Optional idempotency key: any non-empty string (a UUID is recommended; no format is enforced). When provided, replaying the same key returns the original receipt instead of re-running the action; when omitted, no dedupe occurs. Keys are scoped per tool: the same key on another tool is unrelated."
    • addedInput schema / properties / reason / description
      Added value: +"Why the Agent ID is being retired (required, max 500 characters)"
    • addedInput schema / properties / revocation_signature / description
      Added value: +"Hex signature over the exact UTF-8 message agent-id-revoke:<agent_id> (64-char lowercase ID, no trailing newline). EIP-191: personal_sign the message STRING (personal_sign envelope REQUIRED — raw ECDSA will not verify), 0x 65-byte hex r||s||v (v=27/28). ed25519: nacl.sign.detached over the message bytes, 64-byte hex. Signer: the principal's on-file revocation key, or the Embassy signer for cause"
  5. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructive=true and idempotent=true, but the description adds material context the annotations cannot: a $0.25 USDC charge on Base/Arbitrum, the x402 v2 PAYMENT-SIGNATURE header requirement, the paid_url, and who is authorized to sign. It stops short of stating whether revocation is irreversible or what happens to dependent state, which matters for a destructive tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is correctly front-loaded, but the middle of the description is a dense run-on that duplicates the revocation_signature schema description almost verbatim (EIP-191 personal_sign envelope, ed25519 nacl.sign.detached, byte lengths). That redundancy costs space without adding meaning, though the payment and URL details are worth keeping.

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

Completeness5/5

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

For a paid, destructive, signature-gated mutation with a rich input schema and an output schema, the description covers everything the agent needs before calling: cost, chain, payment protocol, docs link, endpoint URL, and signer authority. Return values are correctly left to the output schema.

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 the schema already documents all four parameters, including the full revocation_signature spec that the description largely repeats. The description adds only marginal framing ('64-char lowercase ID', the message format), so the baseline 3 applies.

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 specific verb and resource — 'retire an Agent ID instantly' — which an agent can immediately distinguish from the read-only siblings agentid_verify/agentid_renew. It never names those siblings explicitly, so 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 Guidelines3/5

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

'Use agentid_revoke to retire an Agent ID' is largely a restatement of purpose, and no when-to-use vs. when-to-renew/verify guidance or exclusion criteria is given. The signer eligibility rule (principal's revocation key, or Embassy signer for cause) is the only real usage constraint, and it is framed as a signing detail rather than routing guidance.

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

All Agent Embassy toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources