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

x402 Oracle MCP (Base USDC)

oracle_health

Read-onlyIdempotent

Check x402 Oracle server health, Base payTo posture, facilitator mode, and seller-key safety flags before calling paid consult tools; read-only and free.

Instructions

Check x402 Oracle server health, configured Base payTo posture, facilitator mode (demo or live), and seller-key safety flags. Free and read-only; requires no arguments or payment header. Use this before calling paid consult tools to verify availability; use oracle_pricing to inspect USD fees.

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_health"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
okYesTrue when the Oracle server is healthy and accepting requests.
slugYesCanonical server slug (x402orcle).
thesisNoService thesis motto.
networkYesCAIP-2 settlement network identifier (e.g. eip155:8453).
serviceYesDisplay name of the Oracle service.
versionYesRunning service semver string.
demoModeNoTrue when running with local DemoFacilitator verification.
pay_to_configuredNoTrue when a valid 42-char settlement address is configured.
wallet_configuredNoAlways false on seller-only hosts (no spend key stored).
cdp_auth_configuredNoTrue when Coinbase CDP facilitator JWT credentials are configured.
seller_leak_warningNoTrue only if a dangerous buyer private key was detected in seller env.

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": {
      +    "cdp_auth_configured": {
      +      "description": "True when Coinbase CDP facilitator JWT credentials are configured.",
      +      "type": "boolean"
      +    },
      +    "demoMode": {
      +      "description": "True when running with local DemoFacilitator verification.",
      +      "type": "boolean"
      +    },
      +    "network": {
      +      "description": "CAIP-2 settlement network identifier (e.g. eip155:8453).",
      +      "type": "string"
      +    },
      +    "ok": {
      +      "description": "True when the Oracle server is healthy and accepting requests.",
      +      "type": "boolean"
      +    },
      +    "pay_to_configured": {
      +      "description": "True when a valid 42-char settlement address is configured.",
      +      "type": "boolean"
      +    },
      +    "seller_leak_warning": {
      +      "description": "True only if a dangerous buyer private key was detected in seller env.",
      +      "type": "boolean"
      +    },
      +    "service": {
      +      "description": "Display name of the Oracle service.",
      +      "type": "string"
      +    },
      +    "slug": {
      +      "description": "Canonical server slug (x402orcle).",
      +      "type": "string"
      +    },
      +    "thesis": {
      +      "description": "Service thesis motto.",
      +      "type": "string"
      +    },
      +    "version": {
      +      "description": "Running service semver string.",
      +      "type": "string"
      +    },
      +    "wallet_configured": {
      +      "description": "Always false on seller-only hosts (no spend key stored).",
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "ok",
      +    "service",
      +    "slug",
      +    "version",
      +    "network"
      +  ],
      +  "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. The description adds genuinely non-schema context: it is free and needs no payment header, which matters in an x402 paid-tool ecosystem. It stops short of describing failure modes or output shape, but the output schema covers returns.

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, zero waste, front-loaded with what is checked and followed by when to call it and what to call instead. Dense jargon (payTo, facilitator mode) is domain vocabulary rather than padding.

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?

A zero-parameter, read-only health check with rich annotations and an output schema needs little more than what is here. Availability, cost, and no-auth requirements are all covered, and return values are documented by 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. The description reinforces this by saying it 'requires no arguments or payment header,' which prevents an agent from fabricating inputs or hunting for an auth step.

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 ('Check') and resource ('x402 Oracle server health') and enumerates exactly what is reported: Base payTo posture, facilitator mode (demo or live), and seller-key safety flags. It also distinguishes itself from oracle_pricing and the paid consult tools, so an agent can pick it without opening a 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?

Explicit sequencing guidance: 'Use this before calling paid consult tools to verify availability,' with a named alternative ('use oracle_pricing to inspect USD fees') for a different need. Both the when and the switch-to-other-tool condition are stated, 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.