Bitcompare MCP Server

Official

by bitcompare

Overview Schema Source Related Servers Discussions Admin

Hybrid

Top gainers/losers

top_movers

Read-onlyIdempotent

Identify the biggest 24-hour gainers and losers within a selected rank segment, with adjustable limits per side.

Instructions

Biggest 24h gainers and losers within a rank segment.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Number of gainers and losers to return on each side, default 10
`segment`	No	Rank segment, default "top100"

Output Schema

Name	Required	Description	Default
`losers`	Yes	Top 24h losers in the requested segment
`gainers`	Yes	Top 24h gainers in the requested segment

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jun 15, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive nature, so the description's addition of the 24h time window and rank segment filter is valuable behavioral context. No contradiction with annotations.

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 a single clear sentence with no extraneous information. It perfectly front-loads the core purpose.

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 the simplicity of the tool (2 optional params, full schema coverage, rich annotations, and an output schema), the description is complete enough to guide an agent in correct invocation.

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 schema covers both parameters, but the description adds the 24h time window and clarifies that the rank segment is 'within' a segment, enhancing the semantic understanding beyond the schema alone.

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 the tool returns the biggest 24h gainers and losers within a rank segment, aligning with the name and title. It distinguishes from siblings like 'top_coins' by focusing on movers rather than static ranking.

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?

The description implies usage for querying top performers based on 24h price change, but lacks explicit guidance on when to use it versus similar tools like 'get_price' or 'market_summary'. No alternatives or exclusions are mentioned.

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