Skip to main content
Glama

21btc.cc Bitcoin Data

Rainbow model (a model, not a forecast)

get_rainbow_model
Read-onlyIdempotent

Rainbow model fit parameters and today's deviation (a model, not a forecast). Same data as GET /api/v1/rainbow. Read-only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so 'Read-only' in the description is pure repetition. What the description does add is worth something: the 'not a forecast' caveat sets expectations about the nature of the output, and the REST endpoint mapping lets an agent correlate it with other surfaces. Return shape, units, and refresh cadence are still undisclosed.

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?

A single compact line with the core deliverable front-loaded and no filler. The parenthetical repeats the title verbatim, which is redundant but costs only a few words.

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

Completeness3/5

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

For a zero-parameter read tool this covers the essentials of what is fetched, but with no output schema the agent gets no sense of the structure or scale of the response (scalar fit values? a time series of deviation?). One clause on the return shape would close the remaining gap.

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 takes zero parameters, so per the baseline there is nothing for the description to disambiguate. No misleading parameter language is present.

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?

States a specific resource (rainbow model fit parameters plus today's deviation) rather than restating the name, and the parenthetical 'a model, not a forecast' clarifies what class of data this is. It never names a sibling or explains how it differs from get_price, get_risk_score, or get_stock_to_flow, so it falls short of 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No statement of when to reach for this tool versus the twelve sibling metric tools, and no exclusions. The only orienting clue is 'Same data as GET /api/v1/rainbow,' which is a REST cross-reference rather than agent-facing selection guidance.

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