Skip to main content
Glama

21btc.cc Bitcoin Data

Bitcoin volatility

get_volatility
Read-onlyIdempotent

Annualised realised volatility over 7/30/90/365 days and by year. Same data as GET /api/v1/volatility. 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_volatility"
  }
}

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, so the trailing 'Read-only' adds nothing new. The useful addition is the REST-endpoint equivalence, which helps agents correlate with external docs; beyond that, nothing about response shape or freshness is disclosed.

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?

Two short sentences plus a three-word tag, with the substantive content front-loaded. The closing 'Read-only' is redundant against the annotations and is the one sentence that does not earn its place.

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?

With no output schema and no parameters, the description carries the burden of explaining the return value. It identifies the metric and windows but leaves open whether the result is a time series, a single snapshot per window, and in what units — a meaningful gap for a data-retrieval tool.

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. The description does clarify what the returned figures represent (annualised realised volatility across four window lengths plus yearly breakdowns), which adds meaning about the output even though there are no inputs to document.

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?

Names a specific metric (annualised realised volatility) and its aggregation windows (7/30/90/365 days, by year), which distinguishes it cleanly from siblings like get_price or get_risk_score. It stops short of explicitly contrasting with any sibling, but the resource is unambiguous.

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 statement of when an agent should reach for this tool, nor any named alternative (e.g. get_risk_score or get_price for related signals). The API endpoint reference ('Same data as GET /api/v1/volatility') is a documentation cross-reference, not usage 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