Bitcompare MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

Stablecoin stability leaderboard

stablecoin_index

Read-onlyIdempotent

Compare stablecoins using a ranked leaderboard with stability scores, peg deviation, and market cap to find top performers.

Instructions

Ranked stablecoin leaderboard with stability scores, peg deviation, and market cap.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Default 50

Output Schema

Name	Required	Description	Default
`stablecoins`	Yes	Ranked stablecoin leaderboard

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jun 15, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds context on returned data (stability scores, peg deviation, market cap) but does not go beyond those annotations to disclose behaviors like pagination or update frequency.

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 sentence with no extraneous information. Every word serves a clear 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?

For a simple tool with one optional parameter and an output schema, the description sufficiently explains the purpose and key output fields. No additional context needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a single limit parameter described as 'Default 50'. The description does not add additional meaning beyond that, so baseline score of 3 applies.

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?

Title and description clearly state it provides a ranked leaderboard of stablecoins with stability scores, peg deviation, and market cap. This distinguishes it from sibling tools like stablecoin_peg_stability which may focus on individual peg analysis.

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 obtaining a ranked overview of stablecoins but does not explicitly state when to use it over alternatives (e.g., stablecoin_peg_stability) or when not to use it.

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