Agent Embassy

Correct Copy

correct_copy

Idempotent

$1.00 correction pass on your draft: formatting, links verified live, terms confirmed, leaks scanned — corrected copy + signed report. register sets the voice. 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/copy/correct.

Input Schema

Name	Required	Description
`draft`	Yes	The raw draft copy to correct (1-20000 chars)
`links`	No	HTTPS URLs the copy references; each is verified alive via HEAD (fallback GET), 8s timeout, redirects never followed (max 20)
`register`	Yes	Voice register: founder-notes, elite, force, or bright-soft-junior
`required_terms`	No	Terms that must appear in the final copy (max 20; each term max 100 chars; counted case-insensitively)
`idempotency_key`	Yes	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.

Output Schema

Name	Required	Description
`how`	Yes	How to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
`tool`	Yes	Tool name, e.g. check_url_custom
`asset`	Yes	Settlement asset
`price`	Yes	Exact price, e.g. "$0.25"
`networks`	Yes	EVM CAIP-2 network ids accepted
`paid_url`	Yes	x402-paid HTTPS URL to POST the tool inputs to
`facilitator`	Yes	x402 facilitator
`payment_required`	Yes	Always true: this MCP tool is a payment pointer; the tool itself is monetized via x402.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026

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."

Changed1 schema field changedOct 23, 2026
- changedOutput schema / properties / price / description
```
Previous value: -"Exact price, e.g. \"$0.05\""New value: +"Exact price, e.g. \"$0.25\""
```
Changed1 schema field changedOct 17, 2026
- changedOutput schema / properties / tool / description
```
Previous value: -"Tool name, e.g. ping"New value: +"Tool name, e.g. check_url_custom"
```

Changed2 schema fields changedOct 17, 2026

changedInput schema / properties / register / description

Previous value: -"Voice register: founder-notes, elite, force, or bright"New value: +"Voice register: founder-notes, elite, force, or bright-soft-junior"

changedInput schema / properties / register / enum

Previous value: -[
-  "founder-notes",
-  "elite",
-  "force",
-  "bright"
-]New value: +[
+  "founder-notes",
+  "elite",
+  "force",
+  "bright-soft-junior"
+]

Changed1 schema field changedOct 15, 2026
- changedOutput schema / properties / price / description
```
Previous value: -"Exact price, e.g. \"$0.15\""New value: +"Exact price, e.g. \"$0.05\""
```
Changed1 schema field changedOct 15, 2026
- changedOutput schema / properties / tool / description
```
Previous value: -"Tool name, e.g. verified_check"New value: +"Tool name, e.g. ping"
```

Changed2 schema fields changedOct 4, 2026

changedInput schema / properties / register / description

Previous value: -"Voice register: founder-notes, elite, force, or bright-soft-junior"New value: +"Voice register: founder-notes, elite, force, or bright"

changedInput schema / properties / register / enum

Previous value: -[
-  "founder-notes",
-  "elite",
-  "force",
-  "bright-soft-junior"
-]New value: +[
+  "founder-notes",
+  "elite",
+  "force",
+  "bright"
+]

Changed2 schema fields changedSep 26, 2026

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."

Changed6 schema fields changedSep 24, 2026

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 / draft / description

Added value: +"The raw draft copy to correct (1-20000 chars)"

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 / links / description

Added value: +"HTTPS URLs the copy references; each is verified alive via HEAD (fallback GET), 8s timeout, redirects never followed (max 20)"

addedInput schema / properties / register / description

Added value: +"Voice register: founder-notes, elite, force, or bright-soft-junior"

addedInput schema / properties / required_terms / description

Added value: +"Terms that must appear in the final copy (max 20; each term max 100 chars; counted case-insensitively)"

AddedSep 24, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations declare non-read-only, open-world, idempotent and non-destructive, and the description adds the crucial context those annotations cannot carry: the $1.00 USDC cost, the accepted chains (Base, Arbitrum One), the required payment-signature header, and a docs URL for the protocol. It stops short of failure/refund behavior or what the signed report attests, which keeps it below a 5.

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?

The capability statement is front-loaded and useful, but the price is stated three times ('$1.00 correction pass', 'Paid tool — $1.00', plus the paid URL) and payment logistics are interleaved with the functional description. It is not padded with filler, but repetition of the cost and URL costs it structure points.

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 tool with an output schema, the definition covers what an agent needs to call it correctly: inputs to send, the endpoint, the payment header, the currency and chains. Only the post-payment failure modes and what 'leaks scanned' concretely checks remain 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 all five parameters, including the enum for register and the full idempotency-key contract, are already documented in structured data. The description adds only one extra bit of meaning — 'register sets the voice' — beyond the schema, so the baseline of 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?

The description names a specific verb and resource — a '$1.00 correction pass on your draft' — and enumerates the actual operations (formatting, live link verification, term confirmation, leak scanning) plus the deliverables (corrected copy + signed report). No sibling tool in the list does copy correction, so the agent can distinguish it immediately.

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?

It gives solid invocation guidance (POST the JSON inputs to paid_url with an x402 v2 PAYMENT-SIGNATURE header) and notes 'register sets the voice', but it never states when to choose this tool over an alternative or what kinds of drafts are out of scope. Usage is implied by the artifact type rather than explicitly framed as when/when-not.

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

All Agent Embassy tools Inspect

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

Need Help?