Skip to main content
Glama

Research Paper

research_paper
Idempotent

Research paper: $222.00; $444.00 with the provenance pack, proof included. 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

NameRequiredDescriptionDefault
bundleNoDelivery tier: 'paper' ($222.00) or 'paper+provenance' ($444.00, paper plus the corpus proof pack). Defaults to 'paper'
paper_idYesCatalog ID of the paper, e.g. 'the-discontinuity-20260922'. Unknown IDs are rejected
buyer_aliasNoOptional license display name (3-32 chars: letters, digits, . _ -). Defaults to the first 8 hex chars of the buyer wallet
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.
prior_receipt_idNoOptional prior research_paper receipt id for receipt-carried tier pricing on the paper+provenance bundle

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
    • 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'"
  3. 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\""
  4. Changed1 schema field changed
    • 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'"
  5. 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"
  6. 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\""
  7. Changed1 schema field changed
    • changedOutput schema / properties / tool / description
      Previous value: -"Tool name, e.g. verified_check"New value: +"Tool name, e.g. ping"
  8. Changed1 schema field changed
    • 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'"
  9. Changed3 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. 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"
      +}
  10. Changed5 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 / 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"
  11. Changed1 schema field changed
    • addedInput schema / properties / bundle
      Added value: +{
      +  "type": "string"
      +}
  12. Changed1 schema field changed
    • addedInput schema / properties / buyer_alias
      Added value: +{
      +  "type": "string"
      +}
  13. Changed3 schema fields changed
    • 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'"
  14. Added

TDQS

B3.1/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true), the description discloses the salient behaviour an agent needs: this is a paid call requiring an x402 v2 PAYMENT-SIGNATURE header, priced in USDC on Base or Arbitrum One, with the licence bound to the caller's wallet. It does not contradict the annotations and adds real payment/authentication context they do not carry.

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?

Front-loaded with the price and delivery tiers, then the call mechanics and paid URL. Some waste remains: the price is restated three times ($222.00 appears in the opening and again in the closing sentence) and the paid URL is given only once but the phrasing "$222.00; $444.00 with the provenance pack, proof included" is telegraphic and hard to parse.

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, so return values need not be explained, and all five parameters are fully covered. What remains unaddressed is the fulfilment story — how the paper is actually delivered after payment and what happens if payment or a bad paper_id fails — which matters for a purchase tool with openWorldHint=false.

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% and each parameter is already documented inline, including bundle tiers, idempotency-key replay semantics, and prior_receipt_id. The description only echoes the two price points and the receipt-upgrade tier, adding little meaning beyond the schema — the baseline 3 applies.

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 resource (a research paper) and the commercial nature (licence purchase at $222.00, $444.00 with provenance pack) are clear, but the operative verb is never stated — the agent must infer "purchase/licence" from pricing and payment-header instructions. There is no differentiation from siblings such as diligence_pack or trust_report, which appear to be adjacent paid content products.

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 on when to choose this tool over the adjacent paid-content siblings, and no preconditions spelled out (e.g. that a wallet and funded USDC balance are required before calling). The only implicit usage cue is the prior_receipt_id upgrade path, which is stated as pricing rather than as a when-to-use rule.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.