Skip to main content
Glama

AutoTasker Hub — China Social Data API

btc_usd_rate

BTC price in USD plus 50+ fiat currencies via Blockchain.info. $0.01 USDC.

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

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?

With no annotations, the description must carry the behavioral load; it does disclose the upstream data source (Blockchain.info) and a cost ($0.01 USDC, presumably a paid x402-style call), which is genuinely useful context not available elsewhere. It stops short of stating rate limits, freshness/latency, or whether the USDC charge applies per call.

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 compact sentences, front-loaded with the resource and scoped by source and price. The trailing '$0.01 USDC' is terse enough to be ambiguous about whether it is a per-call charge, but it is not wasted space.

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 tool with no output schema and no annotations, this covers the essentials of what is fetched and from where. It leaves open the response shape (which currency keys appear, precision, timestamp) and the payment mechanics of the stated USDC cost, which an agent needs to call it correctly.

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 no parameter meaning the description could add or omit. The only quibble is that it advertises '50+ fiat currencies' with no parameter to select one, leaving unclear whether all rates come back in one payload.

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 and scope: BTC price in USD, extended with 50+ fiat currencies, sourced from Blockchain.info. An agent can tell this is a spot-price lookup rather than a fee estimator (bitcoin_fees) or a generic FX table, though it never names those siblings explicitly.

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 when-to-use or when-not-to-use guidance. The mention of '50+ fiat currencies' overlaps heavily with the visible fx_rates and erapi_fx siblings, yet the description gives no rule for choosing between them and no prerequisites or exclusions.

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.