Skip to main content
Glama

Bitcoin pro (100 sats L402 or $0.10 USDC x402)

get_btc_pro
Read-only

Oracle data plus Lightning Network capacity/channels and daily mining revenue — use this for ecosystem-level stats. Price: 100 sats (Lightning) or $0.10 USDC on Base (x402). Sample (illustrative, not live): {"status":"success","endpoint":"btc_pro","data":{"market":{"price_usd":97500.0,"change_24h_percent":1.23},"on_chain":{"hash_rate_eh":750.0,"block_height":920000},"lightning":{"capacity_btc":5200.0,"channel_count":12000,"node_count":13000},"mining":{"daily_revenue_btc":450.0,"daily_revenue_usd":43875000.0}},"metadata":{"cost_sats":100}} 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_pro"
  }
}

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

A3.9/5.0
Behavior4/5

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

Annotations only say readOnly and openWorld; the description goes well beyond by disclosing that the first call returns HTTP 402 / payment_required, that settlement only occurs on a 200, and the exact header formats for L402 and x402 v1/v2. That is high-value behavioral context for an unusual paid endpoint. It does not cover pagination or refresh cadence, but neither is material here.

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?

Purpose and price are front-loaded, then a sample payload, then the payment mechanics — a sensible order for a paid tool with no output schema. The inline sample JSON is bulky but earns its place because no output schema exists; some of the header-format detail could be tightened.

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 paid, annotation-light, output-schema-less tool, the description covers price, expected response shape, and the full two-protocol payment handshake including failure conditions. An agent has everything needed to call it, handle the 402, and retry 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 already 100%, so the baseline is 3, but the description adds real meaning by tying the credential parameters to the concrete flow: get the 402, pay, then retry with the macaroon:preimage or the signed x402 payload. It also clarifies that omitting both yields the payment requirements, which reinforces the schema's "omit to receive" wording.

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?

States a specific verb+resource bundle — oracle data plus Lightning capacity/channels and mining revenue — and frames it as "ecosystem-level stats," which implicitly separates it from the price-only siblings. It stops short of naming get_btc_oracle or get_btc_price, so the boundary is inferred rather than explicit.

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 ecosystem-level stats" gives an implied selection rule against narrower price tools, and the payment section explains the retry path. There is no explicit when-not or named alternative, so an agent must infer that get_btc_price is the cheap option for a single quote.

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