BTC Intel

How the BTC Intel Score is published

get_methodology

Read-only

Use for definitions, not data: what the Score is, its five classifications, the record's dates, how it is published and checked, and what live, backtested, historical position and the Delayed date mean. The method itself is private. For Score values use get_score_for_day or get_score_live; for the Intel DCA rules get_plan_rules. Free, no arguments; one text document.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`link`	Yes
`note`	Yes
`text`	No
`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
`title`	No
`access`	No
`source`	Yes
`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.

AddedNov 6, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description's extra disclosure that the call is free, takes no arguments, and returns one text document adds useful shape. It also pre-empts a likely failure mode by stating the method itself is private, so an agent won't keep probing for formula details. Minor gap: no indication of document length or stability/versioning.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: what it contains, the privacy caveat, then the sibling routing. Scope is front-loaded and no sentence is filler.

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?

For a zero-argument documentation lookup with an output schema present, the description covers content scope, cost, format, and alternatives. Nothing needed to invoke 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?

The tool has zero parameters, so the baseline is 4; the description confirms this with "no arguments," matching the empty schema. There is no further parameter meaning to add.

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 resource (the methodology/documentation behind the BTC Intel Score) and explicitly frames it as definitions rather than data, which separates it cleanly from get_score_for_day and get_score_live. The enumerated contents (five classifications, record dates, publication/checking process, live vs backtested vs historical vs Delayed) tell an agent exactly what knowledge it can obtain.

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 when-to-use rule ("for definitions, not data") and names the alternative tools with their selecting conditions: get_score_for_day/get_score_live for values, get_plan_rules for DCA rules. This is a complete routing statement, not an implied one.

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?