Skip to main content
Glama

Bitcoin oracle (50 sats L402 or $0.05 USDC x402)

get_btc_oracle
Read-only

BTC price plus hash rate, mempool, difficulty, fees and block height — use this for a compact network snapshot. Price: 50 sats (Lightning) or $0.05 USDC on Base (x402). Sample (illustrative, not live): {"status":"success","endpoint":"btc_oracle","data":{"market":{"price_usd":97500.0,"price_eur":90120.5,"change_24h_percent":1.23,"stale":false},"on_chain":{"hash_rate_eh":750.0,"mempool_size_tx":15000,"difficulty":110000000000000.0,"block_height":920000},"fees":{"avg_fee_sat_vbyte":8,"fast_fee_sat_vbyte":14,"slow_fee_sat_vbyte":2}},"metadata":{"cost_sats":50}} Pay: Call it, get HTTP 402 (or MCP payment_required) with a Lightning invoice and macaroon, pay the invoice, then retry with Authorization: L402 <macaroon>:<preimage>. Or pay in USDC on Base via x402: sign the 402's x402 requirement (PAYMENT-REQUIRED header, or accepts in the JSON body) and retry with the PAYMENT-SIGNATURE (x402 v2) or X-PAYMENT (v1) header; only a 200 is settled.

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": "get_btc_oracle"
  }
}

Input Schema

NameRequiredDescriptionDefault
x402_paymentNoOptional x402 payment (USDC on Base): base64 PaymentPayload (v2, or v1 X-PAYMENT format) signed for accepts[0] of this tool's payment_required result. Alternative to params._meta['x402/payment']. Omit both to receive the payment requirements.
l402_credentialNoOptional L402 credential '<macaroon>:<preimage_hex>' (or 'L402 <macaroon>:<preimage>') from a paid invoice or an active subscription. Omit it to receive the Lightning invoice and macaroon.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / x402_payment
      Added value: +{
      +  "description": "Optional x402 payment (USDC on Base): base64 PaymentPayload (v2, or v1 X-PAYMENT format) signed for accepts[0] of this tool's payment_required result. Alternative to params._meta['x402/payment']. Omit both to receive the payment requirements.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds the crucial behavioral layer: a dual payment model with exact prices (50 sats / $0.05 USDC), the 402/payment_required handshake, the retry header formats, and the rule that 'only a 200 is settled'. It also flags the 'stale' field in the sample so the agent knows freshness is signaled in the payload.

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

Conciseness3/5

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

Purpose is front-loaded and the payment instructions are logically ordered, but the embedded illustrative JSON sample is bulky and consumes a large share of the text. It is useful for a tool with no output schema, yet it crowds the description and could have been trimmed.

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?

With no output schema, the description carries the full burden of describing returns, and the sample payload covers market, on-chain, fees and metadata fields including cost_sats. The full payment round-trip for both L402 and x402 is spelled out, so an agent has everything needed to call and settle correctly.

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?

Schema coverage is 100%, so both payment parameters are already documented, setting a baseline of 3. The description goes beyond that by explaining the operational semantics of the credentials — get a 402 with a Lightning invoice and macaroon, pay, then retry with the L402 header, or sign the x402 requirement and retry with PAYMENT-SIGNATURE. That clarifies what each optional parameter is actually for.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb-less but concrete resource list — price plus hash rate, mempool, difficulty, fees and block height — and labels it a 'compact network snapshot'. An agent can tell this is the multi-metric variant, though it never names siblings like get_btc_price or get_btc_pro to sharpen the distinction.

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

Usage Guidelines3/5

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

'use this for a compact network snapshot' gives an implied when-to-use context. There is no explicit guidance on when to prefer get_btc_price over this, nor any exclusions, so the agent must infer selection from the sibling names alone.

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.

Resources