BTC Intel

One area of the Bitcoin market, in depth

get_area

Read-only

Use for one named area of the market ("how is on-chain?", "what is liquidity saying?"), as its Analysis page shows it today: the read, how confident it is and when it last changed, the read by horizon (days, weeks, months), the reasoning in plain English (what holds it up, what could change it) and the state of each of its parts. Areas: technical, on-chain, market-structure, sentiment and macro (the five areas of the read), and cross-market (how the five line up), liquidity (the price levels where forced buying and selling sit, funding and the next big options expiry) and cycle (where Bitcoin is in its four-year cycle). For every area at once with the price and the forces use get_bitcoin_today; for the parts of all five areas side by side get_market_detail. Free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "area": "<area>"
    },
    "name": "get_area"
  }
}

Input Schema

Name	Required	Description	Default
`area`	Yes	The area, as named on btcintel.org/analysis/.

Output Schema

Name	Required	Description	Default
`area`	No
`line`	No
`link`	No
`note`	No
`read`	No
`parts`	No
`source`	No
`reasoning`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already establish that this is a read-only, closed-world tool, so the bar is lower. The description adds useful context beyond annotations by saying the result reflects the Analysis page "today," includes confidence and last-changed information, and is free. It does not need to describe rate limits or auth for this read-only endpoint.

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 description is front-loaded with the core use case and alternatives, and every sentence adds selection or semantic value. It is somewhat long and repeats the enum labels already present in the schema, but the parenthetical explanations justify most of the length.

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?

Given the output schema, the description need not restate return fields, and it still explains what the area pages provide at a high level. Combined with clear area semantics and sibling routing, an agent has everything needed to select and invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline would be 3, but the description meaningfully explains each enum value. It clarifies that cross-market is how the five areas line up, that liquidity covers forced buying/selling levels, funding, and options expiry, and that cycle is the four-year cycle position.

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: use for one named area of the Bitcoin market, and it enumerates the eight supported areas. It also distinguishes this from get_bitcoin_today and get_market_detail, so an agent can tell exactly what this tool returns versus its siblings.

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 explicit trigger examples ("how is on-chain?", "what is liquidity saying?") and names the alternatives for broader use: get_bitcoin_today for every area at once, get_market_detail for parts of all five areas side by side. The conditions for choosing among them are clear.

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?