agent-embassy

Give — Support the Embassy

give

Idempotent

Support the Embassy. Open-amount USDC gift, $0.01–$222. The signed quote binds your exact amount; receipt: patronage, never for work. 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 — open amount, buyer chooses $0.01–$222.00, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/give.

Input Schema

Name	Required	Description	Default
`amount_usd`	Yes	Exact gift amount in USD, caller-supplied: a plain decimal string like "5.00" ("$5.00" also accepted) or a number with at most 2 decimals. Canonical integer-cent parse: exponent, locale/grouping, sub-cent precision, negative, zero, below-$0.01 and above-$222.00 forms are rejected. The signed 402 quote binds this exact amount; you authorize exactly what you quoted.
`idempotency_key`	Yes	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.

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 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"
```
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"
```
AddedSep 26, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations cover safety (readOnly=false, destructive=false, idempotent=true) but say nothing about payment behavior; the description adds the paid flow, the binding of the signed quote to the exact amount, the "patronage, never for work" receipt semantics, and the protocol doc link. It stops short of failure/refund behavior, so not 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 invocation guidance is front-loaded, but the amount range and USDC/chain detail are restated twice ("$0.01–$222" early, "$0.01–$222.00, USDC on Base or Arbitrum One" later) and the paid URL appears twice, inflating length without new information.

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?

An output schema covers the receipt, so return values needn't be explained. The description supplies everything an agent needs to actually execute a paid call — URL, method, header, amount constraint, idempotency semantics — leaving only error-path specifics unaddressed.

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 coverage is 100%, so the description's restatement of the amount range and quote binding largely duplicates what the parameters already document. It adds no parsing or idempotency detail beyond the schema, so 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 concrete purpose ("Support the Embassy") plus what it transacts: an open-amount USDC gift bounded $0.01–$222 with the paid URL named. No sibling among the agentid/attest/trust tools does payments, so it is trivially distinguishable.

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?

Explains the invocation mechanics (POST inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header) and the buyer-chosen-amount model, which is the when/how. It doesn't explicitly rule out alternatives, but no sibling overlaps this capability, so the omission is minor.

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.