Skip to main content
Glama
Sign In
Carbon Cashmere MCP Server

Carbon Cashmere MCP Server

Official
by CarbonCashmere
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_v1_btc_derivatives_blocks_range

Extract up to 144 Bitcoin blocks in a single call, returning per-block summaries with height, time, miner pool, transaction stats, and coinbase reward. Pay-per-call pricing.

Instructions

Bulk Bitcoin block extract (max 144 blocks per call = $1.44 cap). Returns array of per-block summaries (height, time, miner pool, tx count, witness/taproot/ordinals/op_return stats, total output, coinbase reward). Price: $0.02. Category: bitcoin-onchain.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A4.4/5.0
Behavior4/5

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

No annotations provided, but description discloses output contents (height, time, miner pool, etc.), limits, and pricing. It implies a read operation but lacks explicit safety or side-effect disclosure.

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?

Description is three sentences, front-loaded with main purpose, then output details, then metadata. No unnecessary words; highly efficient.

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 simple tool with no input parameters and no output schema, the description adequately covers purpose, constraints, and return format. Missing explicit mention of authentication or rate limits, but not critical.

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?

Input schema has zero properties, so no parameters to describe. Baseline is 4; description adds no additional parameter info, but it implicitly conveys the range is determined by the endpoint path.

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?

Description clearly states 'Bulk Bitcoin block extract' with a specific scope (max 144 blocks) and lists output fields. Distinguishes from sibling tools like 'get_v1_btc_derivatives_blocks_height' by indicating it extracts a range.

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?

Description specifies max blocks and price cap, implying usage for batch retrieval. However, it does not explicitly state when to use versus alternative tools (e.g., single block extraction) or provide when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools