Skip to main content
Glama

Bitcoin signals (200 sats L402 or $0.20 USDC x402)

get_btc_signals
Read-only

Fear & Greed, BTC/gold, % from ATH, momentum, volatility and 24h transactions (dominance, NVT and active addresses are null without a licensed source) — use this for market-signal context. Price: 200 sats (Lightning) or $0.20 USDC on Base (x402). Sample (illustrative, not live): {"status":"success","endpoint":"btc_signals","data":{"sentiment":{"fear_greed_index":42,"fear_greed_classification":"Fear"},"market":{"btc_price_usd":97500.0,"btc_dominance_percent":null,"gold_ratio":{"gold_price_usd":2650.0,"btc_gold_ratio":36.79}},"network_activity":{"active_addresses_24h":null,"transactions_24h":450000},"valuation":{"ath_usd":126000.0,"percent_from_ath":-22.6,"nvt_ratio":null},"technicals":{"momentum_score":55,"volatility_regime":"normal"}},"metadata":{"cost_sats":200}} 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_signals"
  }
}

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
Behavior5/5

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

Beyond the thin readOnlyHint/openWorldHint annotations, the description discloses the paywall behaviour that dominates this tool: an initial call returns HTTP 402 (or MCP payment_required) with a Lightning invoice and macaroon, the retry must carry `Authorization: L402 <macaroon>:<preimage>`, and x402 payment settles only on a 200. It also warns which fields are null without a licensed source, which prevents an agent from misreading nulls as errors.

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?

It is front-loaded well — data contents first, then price, then sample, then payment mechanics. But the length is inflated by a large illustrative JSON sample and a dense paragraph of dual-protocol header instructions (x402 v1 vs v2, PAYMENT-SIGNATURE vs X-PAYMENT) that could be tightened considerably.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a payment-gated tool with no output schema, the definition is unusually complete: it supplies a labelled sample response showing the full object shape and explains the null semantics and settlement condition. Only minor gaps remain, such as data refresh cadence and what a failed/non-200 response other than 402 looks like.

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 prose adds real meaning: it explains that both parameters are optional alternatives, that omitting them yields the payment requirements, and how the credential values are obtained ('call it, get 402, pay, retry'). That procedural context is not derivable from the schema field descriptions alone.

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 names the concrete signal set it returns (Fear & Greed, BTC/gold ratio, % from ATH, momentum, volatility, 24h transactions) and frames the use as 'market-signal context', so an agent knows exactly what comes back. It does not, however, contrast itself with near-neighbours like get_btc_oracle, get_btc_pro or get_market_insights, so the boundary between these data tools must be inferred.

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?

Usage is implied rather than stated: 'use this for market-signal context' plus the note that dominance, NVT and active addresses are null without a licensed source hints that a licensed sibling is needed for those fields. There is no explicit when-not-to-use rule and no named alternative for raw price or licensed metrics, so routing guidance is only partial.

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