BTC Intel

Bitcoin today: price, the read and why

get_bitcoin_today

Read-only

Use for "what is Bitcoin doing and why", first: one morning briefing from BTC Intel's published Brief and Full Read. It gives the price now with its 24-hour, 3-day and 12-month moves and the distance from the cycle high; the market read in one sentence; the five areas (Technical, On-chain, Market structure, Sentiment, Macro) with each one's reason and last change; the forces moving the market, each with the figures behind it (for example stablecoin supply, funding, ETF flows, VIX); what changed today, this week and this month; what would change the read; and the events coming up. detail "full" adds the full reasoning and 14 days of calendar instead of 7. For the calendar alone use get_calendar, for one area in depth get_area, for the BTC Intel Score get_score_for_day. The Brief is published at 6 AM ET; the price is rolling. Free.

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

Input Schema

Name	Required	Description	Default
`detail`	No	summary (default): the briefing, about a page of text. full: adds the reasoning and two weeks of events.

Output Schema

Name	Required	Description	Default
`link`	No
`note`	No
`read`	No
`areas`	No
`as_of`	No
`price`	No
`source`	No
`drivers`	No
`calendar`	No
`what_changed`	No
`what_would_change`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 10, 2026
- removedOutput schema / properties / news_tone_48h
```
Removed value: -{
-  "type": [
-    "object",
-    "null"
-  ]
-}
```
- removedOutput schema / properties / top_stories
```
Removed value: -{
-  "type": "array"
-}
```
AddedNov 10, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds freshness and cost context that annotations cannot carry — the Brief publishes at 6 AM ET while the price is rolling, and access is free. It also discloses that the response is a single morning briefing drawn from published Brief/Full Read content, which tells the agent how stale or complete the data may be.

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 use case and the sibling routing are front-loaded, and every clause maps to a real capability of the payload. It is a long single-sentence enumeration, though, and the five-area and forces lists could be compressed without losing selection value.

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 only one optional enum parameter, an output schema present, and annotations covering the read-only profile, the description covers everything an agent needs: what the payload contains, how the detail flag changes it, when it refreshes, cost, and which siblings to prefer. Nothing material 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% and the enum is already documented, so the baseline is 3; the description earns an extra point by quantifying the difference (14 days of calendar instead of 7) rather than merely restating that "full" adds reasoning and events. It also frames "summary" as roughly a page of text, giving a sense of response size the schema does not.

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 opens with a specific use case ("what is Bitcoin doing and why") and then enumerates the concrete contents of the resource: price plus 24h/3-day/12-month moves, cycle-high distance, the one-sentence market read, five named areas, forces with figures, changes over three horizons, invalidation conditions, and upcoming events. It also names the sibling tools it is not (get_calendar, get_area, get_score_for_day), so an agent can separate it from near-neighbours without opening schemas.

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 states when to reach for it ("what is Bitcoin doing and why, first") and routes three specific alternatives to their own conditions: calendar alone, one area in depth, and the BTC Intel Score. This is explicit when-to-use plus alternatives, not implied guidance.

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?