Skip to main content
Glama

Bitcoin price lite (3 sats L402 or $0.005 USDC x402)

get_btc_price_lite
Read-only

BTC price in whole US dollars, refreshed at most every 5 minutes (3 sats) — use this when you only need a rough spot price; no EUR or 24h change (btc_price has both). Price: 3 sats (Lightning) or $0.005 USDC on Base (x402). Sample (illustrative, not live): {"status":"success","endpoint":"btc_price_lite","data":{"price_usd":97500,"stale":false,"timestamp":"2026-11-15T20:00:00Z"},"metadata":{"cost_sats":3}} 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_lite"
  }
}

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. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description must carry the real behavioral burden — and it does: pricing (3 sats / $0.005 USDC), staleness cadence, the HTTP 402 challenge flow, macaroon:preimage retry format, and x402 header variants (PAYMENT-SIGNATURE vs X-PAYMENT). This is far beyond what structured fields provide.

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?

Front-loaded with price, cadence, cost, and the sibling exclusion. The payment paragraph is dense but earns its space; the illustrative sample JSON is the one element that could be trimmed without losing agent-relevant 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?

No output schema exists, yet the description supplies a sample response shape plus timestamps and a stale flag, and it fully documents the payment handshake for a zero-required-parameter paid endpoint. Nothing an agent needs to call it successfully 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 the baseline is 3. The description still adds value by explaining the retry loop that gives the two payment parameters meaning (call, get 402, pay, retry with credential or x402 header), which contextualizes when to supply them.

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 and resource ('BTC price in whole US dollars'), plus scope ('refreshed at most every 5 minutes'), and explicitly names what it is not ('no EUR or 24h change (btc_price has both)'). An agent can distinguish it from get_btc_price and get_btc_price_fresh without opening any 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?

Gives an explicit selection rule ('use this when you only need a rough spot price') and names the sibling that covers the richer case with its differentiating fields. Both when-to-use and when-to-use-something-else are present.

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