Skip to main content
Glama

Bitcoin price (10 sats L402 or $0.01 USDC x402)

get_btc_price
Read-only

Live BTC price in USD/EUR with 24h change, cached up to 60 seconds — use this when you only need the spot price and a one-minute quote is enough. Price: 10 sats (Lightning) or $0.01 USDC on Base (x402). Sample (illustrative, not live): {"status":"success","endpoint":"btc_price","data":{"price_usd":97500.0,"price_eur":90120.5,"change_24h_percent":1.23,"stale":false,"timestamp":"2026-11-15T20:00:00Z"},"metadata":{"cost_sats":10}} 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_price"
  }
}

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.3/5.0
Behavior5/5

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

Annotations only declare read-only and open-world; the description goes much further, disclosing the 60-second cache, the cost (10 sats / $0.01 USDC), the full 402 challenge-and-retry handshake for L402 and x402, and the important detail that 'only a 200 is settled'. These are exactly the behavioral facts an agent cannot get from structured fields.

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 cache caveat are front-loaded, followed by price, then the payment dance. The illustrative sample payload is lengthy but compensates for the absence of an output schema, so it largely earns its space; the payment paragraph is dense but ordered correctly.

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 sample response supplies the return shape (status, data fields, metadata.cost_sats), and the payment instructions cover the only real failure mode: an unpaid 402. There is nothing an agent needs in order to call this correctly that is missing.

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 a 3 is the floor, but the payment-flow prose explains what each parameter is functionally for — obtaining requirements first, then supplying a signed x402 payload or L402 macaroon:preimage on retry. That adds operational meaning beyond the schema's own field descriptions.

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 and resource ('Live BTC price in USD/EUR with 24h change') plus a key trait, 'cached up to 60 seconds', which implicitly separates it from get_btc_price_fresh. It stops short of naming the sibling that a caller should use when a cached minute isn't good enough.

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?

'use this when you only need the spot price and a one-minute quote is enough' gives a clear selection condition and hints that a fresher alternative exists. It never names that alternative or states an explicit when-not to use this tool.

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