agent-embassy

Research Paper

research_paper

Idempotent

The research paper: $222.00; $444.00 with the provenance pack — paper plus its proof. bundle defaults to paper; prior receipt: $222.00 upgrade. Licensed to your wallet. 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 — $222.00, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/research/paper.

Input Schema

Name	Required	Description
`bundle`	No	Delivery tier: 'paper' ($222.00) or 'paper+provenance' ($444.00, paper plus the corpus proof pack). Defaults to 'paper'
`paper_id`	Yes	Catalog ID of the paper, e.g. 'the-discontinuity-20260922'. Unknown IDs are rejected
`buyer_alias`	No	Optional license display name (3-32 chars: letters, digits, . _ -). Defaults to the first 8 hex chars of the buyer wallet
`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.
`prior_receipt_id`	No	Optional prior research_paper receipt id for receipt-carried tier pricing on the paper+provenance bundle

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 30, 2026

changedInput schema / properties / bundle / description

Previous value: -"Delivery tier: 'paper' ($1.00) or 'paper+provenance' ($2.00, paper plus the corpus proof pack). Defaults to 'paper'"New value: +"Delivery tier: 'paper' ($222.00) or 'paper+provenance' ($444.00, paper plus the corpus proof pack). Defaults to 'paper'"

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 23, 2026

changedInput schema / properties / bundle / description

Previous value: -"Delivery tier: 'paper' ($222) or 'paper+provenance' ($444, paper plus the corpus proof pack). Defaults to 'paper'"New value: +"Delivery tier: 'paper' ($1.00) or 'paper+provenance' ($2.00, paper plus the corpus proof pack). Defaults to 'paper'"

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

Changed1 schema field changedSep 26, 2026

changedInput schema / properties / bundle / description

Previous value: -"Delivery tier: 'paper' ($222) or 'paper+provenance' ($444, paper plus the corpus evidence pack). Defaults to 'paper'"New value: +"Delivery tier: 'paper' ($222) or 'paper+provenance' ($444, paper plus the corpus proof pack). Defaults to 'paper'"

Changed3 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. Keys are additionally scoped per payer account: a key never returns another wallet's receipt."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."

addedInput schema / properties / prior_receipt_id

Added value: +{
+  "description": "Optional prior research_paper receipt id for receipt-carried tier pricing on the paper+provenance bundle",
+  "type": "string"
+}

Changed5 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 / bundle / description

Added value: +"Delivery tier: 'paper' ($222) or 'paper+provenance' ($444, paper plus the corpus evidence pack). Defaults to 'paper'"

addedInput schema / properties / buyer_alias / description

Added value: +"Optional license display name (3-32 chars: letters, digits, . _ -). Defaults to the first 8 hex chars of the buyer wallet"

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. Keys are additionally scoped per payer account: a key never returns another wallet's receipt."

addedInput schema / properties / paper_id / description

Added value: +"Catalog ID of the paper, e.g. 'the-discontinuity-20260922'. Unknown IDs are rejected"

Changed1 schema field changedSep 23, 2026
- addedInput schema / properties / bundle
```
Added value: +{
+  "type": "string"
+}
```
Changed1 schema field changedSep 22, 2026
- addedInput schema / properties / buyer_alias
```
Added value: +{
+  "type": "string"
+}
```

Changed3 schema fields changedSep 22, 2026

changedInput schema / properties / agent_wallet / description

Previous value: -"DEV MODE ONLY: wallet to attribute. In live mode the payer wallet from the verified x402 payment is used."New value: +"dev mode only"

removedInput schema / properties / idempotency_key / description

Removed value: -"Client-generated UUID; retries return the original receipt"

removedInput schema / properties / paper_id / description

Removed value: -"Allowlisted paper ID, e.g. 'newly-programmable-economy-20260922'"

AddedSep 22, 2026

TDQS

B3.1/5.0

Behavior4/5

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

Annotations already declare the tool is not read-only and is idempotent. The description adds critical context: it is a paid tool requiring x402 payment, with specific pricing tiers and idempotency key behavior (replays return original receipts). This goes well beyond the annotations.

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 description contains necessary payment details but is repetitive with pricing information and lacks logical flow. It does not front-load the core action, instead starting with a price fragment.

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?

Given the presence of an output schema and annotations, the description provides sufficient behavioral context for a paid tool: payment workflow, licensing, and idempotency semantics. It does not explain the paper's content, but that is likely outside scope.

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 all parameters are documented in the schema. The description adds minor semantics—mentioning bundle defaults and prior receipt upgrade pricing—but does not significantly expand on parameter meanings beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource (a research paper) and its pricing tiers, but lacks a clear action verb like 'purchase' or 'retrieve'. The agent must infer that this is a paid acquisition tool. It does not distinguish from siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternatives. There is no context about scenarios that call for purchasing a research paper, nor any exclusions or comparisons to sibling tools.

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.

Research Paper

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources