Skip to main content
Glama

CoinVet

Bitcoin price (USD, EUR, GBP, CAD, CHF, AUD, JPY)

btc_price
Read-onlyIdempotent

Current Bitcoin price in major fiat currencies from mempool.space, plus sats per currency unit. Indicative, refreshed about every minute.

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": "btc_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
currencyNoFiat code (default USD)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and openWorld, so safety is covered. The description adds genuinely new behavioral context: the upstream source (mempool.space), the ~1-minute refresh cadence, and the caveat that values are indicative — all of which matter for deciding whether to trust/timestamp a result.

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?

One compact sentence with the primary purpose front-loaded, followed by source and freshness qualifiers. No filler, no restatement of the tool name.

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?

With no output schema and a single optional parameter, the description carries the return-value burden well by noting both the fiat price and the sats-per-unit figure. Minor gaps remain around behavior for unsupported currency codes, but nothing essential for a correct call is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter already documents itself as a fiat code defaulting to USD. The description restates the currency dimension only as "major fiat currencies" without adding accepted codes or behavior for an unsupported code, so it adds little beyond the schema.

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 verb+resource (current Bitcoin price in major fiat currencies), names the data source (mempool.space), and adds the secondary return value (sats per currency unit). No sibling in the list offers pricing data, so the tool is unambiguously distinguishable from the validators and fee/lookup tools.

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

Usage Guidelines4/5

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

The word "current" plus "Indicative, refreshed about every minute" gives clear context for when the tool is appropriate and sets expectations that the value is a near-real-time snapshot rather than an authoritative rate. It stops short of explicit when-not guidance (e.g. don't use for settlement/exchange-rate accounting), so it falls just below the top score.

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