Skip to main content
Glama

Agent ID — Renew

agentid_renew
DestructiveIdempotent

Renew an Agent ID: fresh ID, same chain; the old retires. Sign like a revocation. validity_days defaults to standard. Retire outright: agentid_revoke. 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/renew.

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": {
      "agent_id": "<agent_id>",
      "revocation_signature": "<revocation_signature>"
    },
    "name": "agentid_renew"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYesThe Agent ID string returned at issuance (64 hex characters; case-insensitive). Unknown IDs are rejected
validity_daysNoDays until the renewed Agent ID expires; integer 1-730. Defaults to the Embassy standard when omitted
idempotency_keyNoOptional idempotency key: 8-128 printable ASCII characters (no spaces), client-generated, one per logical request — a UUID v4 is recommended; 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:<OLD_agent_id> (64-char lowercase ID, no trailing newline) — the signature covers the OLD Agent ID being retired. 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

NameRequiredDescriptionDefault
howYesHow to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
toolYesTool name, e.g. check_url_custom
assetYesSettlement asset
priceYesExact price, e.g. "$0.25"
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
    • changedInput schema / properties / idempotency_key / description
      Previous 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."New value: +"Optional idempotency key: 8-128 printable ASCII characters (no spaces), client-generated, one per logical request — a UUID v4 is recommended; 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."
  2. Changed1 schema field changed
    • changedOutput schema / properties / price / description
      Previous value: -"Exact price, e.g. \"$0.05\""New value: +"Exact price, e.g. \"$0.25\""
  3. Changed1 schema field changed
    • changedOutput schema / properties / tool / description
      Previous value: -"Tool name, e.g. ping"New value: +"Tool name, e.g. check_url_custom"
  4. 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\""
  5. Changed1 schema field changed
    • changedOutput schema / properties / tool / description
      Previous value: -"Tool name, e.g. verified_check"New value: +"Tool name, e.g. ping"
  6. 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."
  7. 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 / revocation_signature / description
      Added value: +"Hex signature over the exact UTF-8 message agent-id-revoke:<OLD_agent_id> (64-char lowercase ID, no trailing newline) — the signature covers the OLD Agent ID being retired. 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"
    • addedInput schema / properties / validity_days / description
      Added value: +"Days until the renewed Agent ID expires; integer 1-730. Defaults to the Embassy standard when omitted"
  8. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that this is a paid mutation requiring an x402 v2 PAYMENT-SIGNATURE header, costs $0.25 in USDC on Base or Arbitrum One, and must be invoked by POSTing JSON to the given paid URL. It also clarifies that renewing retires the old ID and that the signature is over the old Agent ID, which materially explains the destructive behavior.

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?

The description is front-loaded with the purpose and retirement behavior, then moves to signing, default validity, the alternative tool, and payment details. It is dense but efficient, with only minor fragmentation in the payment sentences.

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-based mutation, the description covers the essential invocation mechanics: the paid URL, POST body instruction, x402 v2 payment header, price, and accepted networks. The schema and output schema handle parameter details and return values, so the description is complete enough for an agent to call it correctly.

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 fully documents agent_id, validity_days, idempotency_key, and revocation_signature. The description adds only a light reminder that validity_days defaults to standard and that signing works like a revocation; the detailed signature format and idempotency semantics remain in the schema.

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?

The description states a specific verb and resource: 'Renew an Agent ID,' and explains the exact outcome: 'fresh ID, same chain; the old retires.' It also distinguishes the operation from the sibling tool agentid_revoke by naming it explicitly for outright retirement.

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?

The description gives clear usage context: renew to replace an Agent ID while preserving the chain, and use agentid_revoke to retire outright. It does not spell out every eligibility condition or compare with agentid_issue, but the main alternative is named with its distinguishing purpose.

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