Skip to main content
Glama
bitcompare

Bitcompare MCP Server

Official

Global market summary

market_summary
Read-onlyIdempotent

Get a single summary of total market cap, 24h volume, BTC and ETH dominance, and recent trend for the crypto market.

Instructions

One-call summary of total market cap, 24h volume, BTC/ETH dominance, and recent trend.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
trend24hNo24h trend as a decimal (0.02 = +2%)
btcDominanceYesBTC share of total market cap, 0-100
ethDominanceYesETH share of total market cap, 0-100
volume24hUsdYesCombined 24h trading volume
totalMarketCapUsdYesCombined market cap of all tracked coins
Behavior3/5

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

Annotations already indicate readOnly, idempotent, non-destructive. Description adds that it returns summary metrics, which is useful but doesn't disclose further behavioral traits like caching or performance. No contradictions.

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?

Single, front-loaded sentence that efficiently conveys the tool's purpose. No wasted words, and the structure is optimal for quick comprehension.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no parameters and an existing output schema, the description fully covers what an agent needs to know: it returns aggregated market metrics. The listed items (market cap, volume, dominance, trend) are sufficient for understanding the scope.

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?

No parameters, so schema description coverage is 100%. The description adds context about the returned metrics beyond the schema, making it clear what the tool provides without needing param details.

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?

Clearly states it provides a summary of total market cap, 24h volume, BTC/ETH dominance, and recent trend. The verb 'summary' and resource 'global market' are specific. It distinguishes from siblings like coin_markets (individual coins) and top_coins (list) by being an aggregated overview.

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?

Implied usage for a quick overview of global market metrics, but no explicit guidance on when to use vs. alternatives like coin_markets or fear_greed_index. No exclusions or caveats mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bitcompare/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server