Skip to main content
Glama

21btc.cc Bitcoin Data

Bitcoin price

get_price
Read-onlyIdempotent

Live BTC price in USD and 7 other currencies (official FX reference rates). Same data as GET /api/v1/price. 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_price"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already cover readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the description's 'Read-only' is largely redundant. It adds useful context beyond annotations with 'Live' (freshness implication) and 'official FX reference rates' (data provenance), but does not address caching, update frequency, or stale data behavior.

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 short sentences, front-loaded with the core value proposition and with no wasted words. The API endpoint reference and read-only note are compactly appended.

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, no-output-schema tool, the description gives enough context to call it correctly: what data is returned, currency coverage, and the underlying API endpoint. It stops short of describing response shape or freshness guarantees, but those are secondary here.

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?

With zero parameters, the baseline is 4. The description usefully clarifies that the tool returns all currencies (USD plus 7 others) rather than accepting a currency selector, which is meaningful scope information even without a schema.

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?

The description states a specific resource and scope: live BTC price across USD plus 7 other currencies, with official FX reference rates. It's clearly distinct from sibling metrics like get_volatility or get_network_stats, though it doesn't explicitly name a contrasting sibling. A minor deduction because the verb is implied by the tool name rather than stated in the description.

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

Usage Guidelines3/5

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

The description implies the use case (fetch live BTC price) and notes it maps to GET /api/v1/price, but it gives no explicit when-to-use or when-not-to-use guidance relative to alternatives. For a simple, unambiguous price endpoint the implied guidance is adequate, but it's not proactive.

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