Skip to main content
Glama

21btc.cc Bitcoin Data

Stock-to-flow model (a model, not a forecast)

get_stock_to_flow
Read-onlyIdempotent

Stock-to-flow ratio and PlanB 2019 model value (a model, not a forecast). Same data as GET /api/v1/stock-to-flow. 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_stock_to_flow"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so 'Read-only' in the description earns no credit. The description does add genuine interpretive context beyond the structured fields: the output is model-derived and should not be treated as a forecast, which matters for how an agent presents the numbers.

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 a single tight sentence plus a short qualifier, front-loaded with the resource name. Minor waste: 'a model, not a forecast' appears in both title and description, and 'Read-only.' redundantly restates the readOnlyHint annotation.

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

Completeness4/5

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

For a zero-parameter, read-only, no-output-schema metric endpoint, the description gives enough: what the value is, its provenance (PlanB 2019), and the caveat about interpretation. 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 takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. Schema coverage is 100% and the empty object with additionalProperties=false is self-explanatory.

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 (stock-to-flow ratio and PlanB 2019 model value) and pins it to a concrete API endpoint, so the agent knows exactly what data comes back. It does not differentiate itself from closely related siblings such as get_rainbow_model or get_price, which offer alternative valuation/price views.

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?

There is no explicit statement of when to call this versus siblings like get_rainbow_model, nor any prerequisites or exclusions. The only usage-adjacent hint is the repeated caveat 'a model, not a forecast', which implies interpretation caution but not selection criteria.

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