Skip to main content
Glama
x402 Oracle MCP (Base USDC)

x402 Oracle MCP (Base USDC)

oracle_ask

Ask technical or ranking questions about x402 micropayments, MCP monetization, A2A agent cards, and CDP Bazaar discovery; paid USDC queries return actionable guidance and payment challenge details.

Instructions

Ask a general architectural or ranking question about x402 micropayments, MCP monetization, A2A agent cards, or CDP Bazaar discovery ($0.10 USDC on Base). Unpaid calls return an HTTP 402 challenge envelope (isError: true); retry with _meta['x402/payment']. Use oracle_diagnose_402 instead to inspect a raw PAYMENT-REQUIRED header.

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": {
      "question": "<question>"
    },
    "name": "oracle_ask"
  }
}

Input Schema

NameRequiredDescriptionDefault
audienceNoTarget framing for the returned verdict and implementation prompt ('agent', 'developer', or 'operator').agent
questionYesSpecific technical question on x402 wire format, MCP payment wrapping, A2A discovery, or Bazaar ranking.

Output Schema

NameRequiredDescriptionDefault
riskYesPrimary operational or financial failure mode to avoid.
wisdomYesConcise domain guidance grounded in x402/Bazaar production rules.
receiptNoVerified x402 or demo settlement receipt metadata.
verdictYesShort machine-readable classification of the root cause or answer.
citationsYesAuthoritative documentation URLs.
implementation_promptNoReady-to-run SYSTEM/USER developer prompt to apply the fix.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.1.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / audience / default
      Added value: +"agent"
    • addedInput schema / properties / audience / description
      Added value: +"Target framing for the returned verdict and implementation prompt ('agent', 'developer', or 'operator')."
    • addedInput schema / properties / audience / enum
      Added value: +[
      +  "agent",
      +  "developer",
      +  "operator"
      +]
    • addedInput schema / properties / question / description
      Added value: +"Specific technical question on x402 wire format, MCP payment wrapping, A2A discovery, or Bazaar ranking."
    • addedInput schema / properties / question / minLength
      Added value: +1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "citations": {
      +      "description": "Authoritative documentation URLs.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "implementation_prompt": {
      +      "description": "Ready-to-run SYSTEM/USER developer prompt to apply the fix.",
      +      "type": "string"
      +    },
      +    "receipt": {
      +      "description": "Verified x402 or demo settlement receipt metadata.",
      +      "type": "object"
      +    },
      +    "risk": {
      +      "description": "Primary operational or financial failure mode to avoid.",
      +      "type": "string"
      +    },
      +    "verdict": {
      +      "description": "Short machine-readable classification of the root cause or answer.",
      +      "type": "string"
      +    },
      +    "wisdom": {
      +      "description": "Concise domain guidance grounded in x402/Bazaar production rules.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "verdict",
      +    "wisdom",
      +    "risk",
      +    "citations"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: the exact cost ($0.10 USDC on Base), the failure mode of unpaid calls (HTTP 402 challenge envelope with `isError: true`), and the retry mechanism key. That is a meaningful disclosure the annotations alone (readOnlyHint=false, openWorldHint=true) do not convey, though it does not mention rate limits or latency for an open-ended LLM-backed oracle.

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?

Three tight sentences, front-loaded with purpose and topic scope, followed by payment behavior and the sibling reference — nothing is filler. The only redundancy is the price, which is repeated from the annotation title.

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

Completeness5/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 no explanation; the remaining burdens — cost, payment challenge handling, retry path, and scope boundaries — are all covered. For a two-parameter, paid, open-ended consult tool this is complete enough to invoke correctly on the first attempt.

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 both `question` and `audience` are already fully documented, setting the baseline at 3. The description narrows the question scope to 'architectural or ranking' topics, which adds some framing, but it never mentions the `audience` parameter or how it changes the returned verdict.

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 verb ('Ask') plus the exact resource domains it covers (x402 micropayments, MCP monetization, A2A agent cards, CDP Bazaar discovery) and pins the price ($0.10 USDC on Base). It explicitly contrasts itself with oracle_diagnose_402, so an agent can discriminate without opening either schema.

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

Usage Guidelines5/5

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

Names the condition that selects the alternative — 'Use oracle_diagnose_402 instead to inspect a raw PAYMENT-REQUIRED header' — which is a precise routing rule rather than a vague 'see also'. It also tells the caller what to do on the unpaid path (retry with `_meta['x402/payment']`), which is the main invocation decision for this tool.

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