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

x402 Oracle MCP (Base USDC)

complete_oracle_task

Generate end-to-end x402 production launch plans with typed diffs, security constraints, operator handoff checklists, and ship verification steps; use for delivery planning, not short Q&A.

Instructions

Execute a high-depth outcome planning task delivering typed diffs, security constraints, operator handoff checklists, and ship verification steps for an x402 production launch goal ($10.00 USDC on Base). Unpaid calls return 402 terms. Use for end-to-end delivery plans; use oracle_ask ($0.10) for shorter Q&A.

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": {
      "goal": "<goal>"
    },
    "name": "complete_oracle_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalYesConcrete production delivery objective (e.g. 'List oracle_ask on CDP Bazaar after first mainnet settle').
constraintsNoOptional security, budget, or hosting constraints (e.g. 'seller-only host, no EVM_PRIVATE_KEY').

Output Schema

NameRequiredDescriptionDefault
riskNoKey deployment, facilitator, or settlement hazards.
wisdomYesEnd-to-end operational runbook from validation through settlement.
verdictYesOutcome ship classification.
citationsNoSupporting x402 protocol documentation links.
implementation_promptNoComprehensive execution prompt enforcing seller safety.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / constraints / description
      Added value: +"Optional security, budget, or hosting constraints (e.g. 'seller-only host, no EVM_PRIVATE_KEY')."
    • addedInput schema / properties / goal / description
      Added value: +"Concrete production delivery objective (e.g. 'List oracle_ask on CDP Bazaar after first mainnet settle')."
    • addedInput schema / properties / goal / minLength
      Added value: +1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "citations": {
      +      "description": "Supporting x402 protocol documentation links.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "implementation_prompt": {
      +      "description": "Comprehensive execution prompt enforcing seller safety.",
      +      "type": "string"
      +    },
      +    "risk": {
      +      "description": "Key deployment, facilitator, or settlement hazards.",
      +      "type": "string"
      +    },
      +    "verdict": {
      +      "description": "Outcome ship classification.",
      +      "type": "string"
      +    },
      +    "wisdom": {
      +      "description": "End-to-end operational runbook from validation through settlement.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "verdict",
      +    "wisdom"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare openWorldHint=true, readOnlyHint=false, non-idempotent, non-destructive; the description adds genuinely new behavior by disclosing that unpaid calls return 402 terms and that the call costs $10.00 USDC on Base. That is non-obvious economic and gating context an agent cannot get from annotations or schema. It stops short of covering failure/retry behavior or turnaround time.

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?

Two sentences, front-loaded with the deliverable set before the routing advice, and nothing is padded. The first sentence is a long comma-chained list that takes effort to parse, which slightly hurts scannability.

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 exists, so return format need not be explained, yet the description still sketches the deliverable shape. With only two well-documented params and annotations covering safety, the only gap is operational detail such as latency, retry semantics, or what a partial failure looks like.

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% and both parameters carry their own descriptions including examples, so the schema does the heavy lifting. The description only implicitly reinforces 'goal' as a production launch objective and adds nothing about how 'constraints' shapes the output. 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?

Uses a specific verb ('Execute') with a named resource ('high-depth outcome planning task') and enumerates concrete deliverables: typed diffs, security constraints, operator handoff checklists, ship verification steps. It also anchors the scope to an x402 production launch goal ($10.00 USDC on Base), so an agent can distinguish it from oracle_ask 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 Guidelines4/5

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

Explicitly routes the agent: 'Use for end-to-end delivery plans; use oracle_ask ($0.10) for shorter Q&A.' That names an alternative and the condition that selects it, plus a price contrast. It does not state explicit when-not or prerequisite conditions (e.g. requires wallet funding), so it falls short of a full 5.

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