Skip to main content
Glama
Sign In

Agent Embassy

by pro.aemb
OverviewDiscussionsAdmin

Register Recovery

register_recovery
Idempotent

Escrow an encrypted recovery blob: stored opaquely — we cannot decrypt it — for operator review, signed receipt proving its hash; quorum_rules govern release. 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 — $1.00, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/recovery/register.

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": {
      "contact_name": "<contact_name>",
      "quorum_rules": "<quorum_rules>",
      "recovery_blob": "<recovery_blob>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "register_recovery"
  }
}

Input Schema

NameRequiredDescriptionDefault
contact_nameYesYour name or operator handle, recorded with the escrow
quorum_rulesYesThe release rules for this blob, e.g. '2-of-3 named trustees must approve release'
recovery_blobYesClient-encrypted blob (ENC:v1:base64...). Stored opaquely; only its SHA-256 and byte count enter the signed receipt
contact_handleNoOptional contact (email or handle) for the operator review
idempotency_keyYesIdempotency key: 8-128 printable ASCII characters (no spaces), client-generated, one per logical request — a UUID v4 is recommended. Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins even if you resend different inputs. Published example keys are rejected. Keys are scoped per tool and per payer account: a key never returns another wallet's receipt.

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: -"Idempotency key: UUID v4, client-generated, one per logical request. Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins even if you resend different inputs. Published example keys are rejected. Keys are scoped per tool and per payer account: a key never returns another wallet's receipt."New value: +"Idempotency key: 8-128 printable ASCII characters (no spaces), client-generated, one per logical request — a UUID v4 is recommended. Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins even if you resend different inputs. Published example keys are rejected. Keys are scoped per tool and per payer account: a key never returns another wallet's receipt."
  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: -"Idempotency key: any non-empty string (a UUID is recommended; no format is enforced). Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins even if you resend different inputs. Keys are scoped per tool: the same key on another tool is unrelated."New value: +"Idempotency key: UUID v4, client-generated, one per logical request. Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins even if you resend different inputs. Published example keys are rejected. Keys are scoped per tool and per payer account: a key never returns another wallet's receipt."
  7. Changed6 schema fields changed
    • 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 / contact_handle / description
      Added value: +"Optional contact (email or handle) for the operator review"
    • addedInput schema / properties / contact_name / description
      Added value: +"Your name or operator handle, recorded with the escrow"
    • addedInput schema / properties / idempotency_key / description
      Added value: +"Idempotency key: any non-empty string (a UUID is recommended; no format is enforced). Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins even if you resend different inputs. Keys are scoped per tool: the same key on another tool is unrelated."
    • addedInput schema / properties / quorum_rules / description
      Added value: +"The release rules for this blob, e.g. '2-of-3 named trustees must approve release'"
    • addedInput schema / properties / recovery_blob / description
      Added value: +"Client-encrypted blob (ENC:v1:base64...). Stored opaquely; only its SHA-256 and byte count enter the signed receipt"
  8. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations (destructiveHint=false, idempotentHint=true), the description discloses the important behavioral trait that the blob is stored opaquely and cannot be decrypted by the service, that only its hash and byte count enter a signed receipt, and that release is quorum-governed. It also states the paid nature, price, and network up front. It stops short of describing failure modes, review turnaround, or what an operator can and cannot do with the escrow.

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 core purpose is front-loaded in the first clause, with payment and endpoint mechanics after it, which is the right order for a paid tool. The sentence is dense and semicolon-chained, mixing escrow semantics with transport details, but almost every element carries operational weight for a payable endpoint.

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 write tool whose return shape is already covered by an output schema, the description supplies the encryption posture, receipt semantics, quorum governance, and full payment invocation details. Remaining gaps — what operator review entails downstream and how release is subsequently triggered — are adjacent concerns rather than blockers to calling it correctly.

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; the description earns one more by reinforcing the semantics that matter most — that recovery_blob must be client-encrypted and is stored opaquely, and that quorum_rules are the release policy rather than free-form metadata. It adds context but no new format details beyond what the schema already documents.

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 ('Escrow an encrypted recovery blob') plus the outcome: opaque storage, operator review, a signed receipt proving the hash, and quorum_rules governing release. No sibling tool overlaps with recovery escrow, so an agent can identify this as the distinct registration path 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 Guidelines3/5

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

Usage is implied rather than stated: an agent infers this is the tool for depositing a client-encrypted recovery secret under quorum rules. There is no explicit when-to-use/when-not guidance, no mention of a companion retrieval or release tool, and no prerequisites beyond the payment mechanics. The invocation instructions (POST to paid_url with an x402 header) are operational, not selection 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