BTC Intel

BTC Intel Score momentum

get_score_momentum

Read-only

Use for recent change: how many points the Score moved over 1, 7, 30 and 90 days, and how many days it has held its current classification. Choose it to see whether the Score is rising or falling; for the values themselves use get_score_history, for averages and distributions get_score_statistics, for past classification periods get_classification_history. Free through the Delayed date (the free cut-off, three months before the latest published day). live = true reaches the latest published day and costs $0.25 in bitcoin over Lightning, one payment per answer, no subscription: the first call returns an invoice instead of data (steps under payment). Changes describe the past, not what comes next.

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_score_momentum"
  }
}

Input Schema

Name	Required	Description	Default
`live`	No	true: data through the latest published day, paid ($0.25). Omit or false: the free answer, through the Delayed date.
`payment`	No	Omit on the first call: a paid request then returns a Lightning invoice (valid 10 minutes) and a macaroon instead of data. Pay it, then repeat the call with the same other arguments and payment = "<macaroon>:<preimage>" (the preimage your wallet shows once paid) within 24 hours. A used, expired or mismatched proof is refused with the reason; call again without payment for a new invoice.

Output Schema

Name	Required	Description
`link`	Yes
`note`	Yes
`as_of`	Yes	UTC: the last day the answer covers (YYYY-MM-DD), or for the Brief and methodology the time it was published (ISO 8601)
`pages`	No
`range`	No
`access`	No
`source`	Yes
`through`	No
`momentum`	No
`price_usd`	No
`basis_note`	No
`score_note`	No
`attribution`	Yes
`delayed_through`	No	The Delayed date: free answers stop here
`payment_required`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 7, 2026

changedInput schema / properties / live / description

Previous value: -"Set true for data through the latest published day (paid, $0.25 a call). Leave out for the free answer, which stops at the Delayed date."New value: +"true: data through the latest published day, paid ($0.25). Omit or false: the free answer, through the Delayed date."

changedInput schema / properties / payment / description

Previous value: -"Leave out at first. After paying the invoice a paid call returned, send \"<macaroon>:<preimage>\" with the same arguments to receive the answer."New value: +"Omit on the first call: a paid request then returns a Lightning invoice (valid 10 minutes) and a macaroon instead of data. Pay it, then repeat the call with the same other arguments and payment = \"<macaroon>:<preimage>\" (the preimage your wallet shows once paid) within 24 hours. A used, expired or mismatched proof is refused with the reason; call again without payment for a new invoice."

Changed2 schema fields changedNov 7, 2026

changedInput schema / properties / live / description

Previous value: -"Optional: true for data through the latest published day (paid, $0.25 a call). Free answers stop at the Delayed date."New value: +"Set true for data through the latest published day (paid, $0.25 a call). Leave out for the free answer, which stops at the Delayed date."

changedInput schema / properties / payment / description

Previous value: -"Optional: \"<macaroon>:<preimage>\" after paying the invoice a paid call returned. Send the same arguments again with it."New value: +"Leave out at first. After paying the invoice a paid call returned, send \"<macaroon>:<preimage>\" with the same arguments to receive the answer."

AddedNov 6, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond readOnlyHint/openWorldHint, the description discloses the two-tier access model: free through the Delayed date (defined as three months before the latest published day), and live=true reaching the latest published day for $0.25 in bitcoin over Lightning, one payment per answer with no subscription. It also states the non-obvious two-step behavior that a paid first call returns an invoice instead of data, which the agent could not infer otherwise.

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?

The purpose and the free/paid split are front-loaded, and every sentence carries information — alternatives, cutoff definition, payment steps, and a scope caveat. It is dense and slightly run-on in the payment clause ('one payment per answer, no subscription'), but nothing is redundant.

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?

An output schema exists, so return values need not be explained; the description instead covers the things the schema cannot — the free versus paid boundary, the invoice-first call sequence, and the interpretation limit. For a two-parameter read tool with a paid path, nothing an agent needs in order to call it correctly 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, and the description adds real meaning on top: it defines the otherwise opaque 'Delayed date' cutoff and ties live=true to a concrete price and payment mechanism. The macaroon/preimage flow is left largely to the schema's payment field description, so it does not fully exceed the schema.

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?

The description states a specific verb and resource — how many points the Score moved over 1, 7, 30 and 90 days and how long it has held its current classification — and explicitly contrasts it with get_score_history, get_score_statistics and get_classification_history. An agent can distinguish it from every relevant sibling without opening a 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?

It gives an explicit selection rule ('Choose it to see whether the Score is rising or falling') and routes three adjacent needs to named alternatives with the condition that selects each. It also flags a scope limit — changes describe the past, not what comes next — so the agent will not misuse it as a forecast.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All BTC Intel tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?