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

x402 Oracle MCP (Base USDC)

oracle_pricing

Read-onlyIdempotent

List free and paid x402 Oracle endpoints, clamped USDC prices on Base, max price ceiling, and connection instructions so you can choose a consult tool and budget payment.

Instructions

List all free and paid x402 Oracle endpoints, current clamped USDC prices on Base, max price ceiling, and connection instructions. Free and read-only; takes no parameters. Call this instead of oracle_health when selecting a paid consult tool and budgeting payment amount.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "oracle_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
freeYesList of free tool descriptors.
paidYesList of paid tool descriptors with priceUsd.
payToYesRecipient USDC address on Base.
connectNoInstructions for connecting over HTTP 402, MCP, and A2A.
networkYesCAIP-2 settlement network (eip155:8453).
maxPriceUsdYesUpper USD price cap enforced on all consults.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / required
      Added value: +[]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "connect": {
      +      "description": "Instructions for connecting over HTTP 402, MCP, and A2A.",
      +      "type": "object"
      +    },
      +    "free": {
      +      "description": "List of free tool descriptors.",
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "maxPriceUsd": {
      +      "description": "Upper USD price cap enforced on all consults.",
      +      "type": "number"
      +    },
      +    "network": {
      +      "description": "CAIP-2 settlement network (eip155:8453).",
      +      "type": "string"
      +    },
      +    "paid": {
      +      "description": "List of paid tool descriptors with priceUsd.",
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "payTo": {
      +      "description": "Recipient USDC address on Base.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "maxPriceUsd",
      +    "network",
      +    "payTo",
      +    "free",
      +    "paid"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds genuinely new behavioral facts not in annotations: the call is free, it takes no parameters, and it discloses the price-clamping/ceiling model the agent will read. It stops short of describing pagination or response shape, but the output schema carries that.

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

Conciseness5/5

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

Two sentences, no filler: the first front-loads what is returned, the second front-loads the cost/read-only constraint and the sibling routing rule. Every clause carries distinct information.

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?

For a no-parameter, read-only listing tool with an output schema and full annotation coverage, the description supplies everything needed to choose and invoke it. Return-value detail is appropriately delegated to the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, so the baseline is 4, and the description correctly and explicitly states 'takes no parameters,' confirming the empty schema is intentional rather than truncated. No additional parameter meaning is needed.

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 specific verb ('List') and a well-defined resource ('free and paid x402 Oracle endpoints'), and enumerates what the listing contains: clamped USDC prices on Base, max price ceiling, and connection instructions. It also names the sibling it substitutes for (oracle_health), so an agent can separate the two without inspecting schemas.

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?

Explicit routing: 'Call this instead of oracle_health when selecting a paid consult tool and budgeting payment amount.' That gives both the condition that selects this tool (choosing/budgeting a paid consult) and the concrete alternative it should replace, leaving nothing to inference.

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