Bitcoin-MCP-Server

Overview Schema Source Related Servers Discussions Admin

get_cryptomarket_overview

Retrieve a comprehensive overview of global cryptocurrency market including total active coins, trading markets, market cap change, ICO status, total market cap and volume, and top 5 dominant cryptocurrencies.

Instructions

Use this to get a comprehensive overview of the global cryptocurrency market conditions and metrics.

Returns detailed metrics in string format:
- Total number of active cryptocurrencies
- Total number of trading markets
- Overall market cap percentage change
- ICO status breakdown (upcoming, ongoing, ended)
- Total market capitalization (formatted by currency)
- Total trading volume (formatted by currency)
- Top 5 cryptocurrencies by market dominance percentage

Use cases: When you need a broad view of the entire crypto ecosystem health, to understand market trends, or to see which cryptocurrencies dominate the market.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Feb 21, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations exist, so description carries full burden. It describes the return format as string and lists metrics, but does not disclose potential behaviors like caching, update frequency, or authentication requirements.

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?

The description is concise, front-loaded with the main purpose, uses bullet points for clarity, and contains no redundant information.

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?

Given the tool has no parameters and no annotations, the description adequately covers purpose and return content. However, it could mention if the output is structured despite claiming string format, as an output schema exists.

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 has no parameters, and schema coverage is 100%. The description adds no parameter info because none are needed. Baseline score of 4 for zero-parameter tools is appropriate.

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?

The description clearly states it provides a comprehensive overview of global cryptocurrency market conditions and metrics, listing specific return values. It is distinct from sibling tools that focus on specific coins or network details.

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?

Explicit use cases are given (e.g., when needing a broad view, market trends, market dominance). The context of sibling tools helps differentiate, but no explicit 'when-not-to-use' is provided.

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