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.

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": {
      "paper_id": "<paper_id>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "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: 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.
`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 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 29, 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"

First observedSep 23, 2026

TDQS

C2.9/5.0

Behavior4/5

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

Annotations already declare idempotentHint=true, destructiveHint=false, and readOnlyHint=false, so the description's main job is to add the payment context — and it does: exact prices, USDC settlement on Base or Arbitrum One, license bound to the buyer's wallet, and the x402 v2 PAYMENT-SIGNATURE handshake with a docs link. It stops short of disclosing failure/refund behavior, settlement timing, or what happens if payment is rejected, and the instruction to "POST the tool inputs as JSON to paid_url" is ambiguous about whether the agent invokes the tool normally or makes an external HTTP call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a run-on of em-dash fragments front-loaded with price rather than purpose, and it repeats the figures redundantly ($222.00 appears three times, $444.00 twice, plus "Paid tool — $222.00"). The actionable invocation detail (POST to paid_url with PAYMENT-SIGNATURE) is buried mid-paragraph rather than leading.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and parameter coverage is complete, so the description doesn't need to explain return values, and the annotations cover the safety profile. What remains thin for a paid mutation tool is the payment lifecycle (when funds are captured relative to paper delivery, what a failed or underpaid request looks like) and the ambiguity of the external-POST instruction, which could lead an agent to call it incorrectly.

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 every parameter (bundle tiers, paper_id rejection behavior, buyer_alias format, idempotency replay semantics, prior_receipt_id pricing) is already fully documented in the schema. The description's pricing and upgrade mentions largely duplicate the bundle and prior_receipt_id descriptions, adding no new parameter meaning; baseline 3 is appropriate.

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 conveys that this is a paid purchase of a research paper licensed to the buyer's wallet, with an optional provenance bundle, but it never states a clean verb+resource sentence — the first clause is a price list ("The research paper: $222.00; $444.00 with the provenance pack"). It also gives no differentiation from siblings like diligence_pack or attest_document, which an agent could plausibly confuse with a research/attestation purchase.

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?

The only usage guidance is about the bundle tier and the prior-receipt upgrade path, which is parameter selection, not tool selection. There is no statement of when to choose this over sibling tools, no prerequisites (e.g., wallet/funding requirements), and no exclusion conditions.

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?