Skip to main content
Glama
bitcompare

Bitcompare MCP Server

Official

Similar coins

similar_coins
Read-onlyIdempotent

Find coins related to a given coin by category or sector similarity. Provide the canonical coin ID to retrieve a list of related coins, optionally limiting the number.

Instructions

Coins related to the given coin by category/sector similarity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax related coins to return, default 10
coinIdYesCanonical coin id to find related coins for (e.g. "bitcoin")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinsYes
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive. The description adds the mechanism (category/sector similarity), providing useful behavioral context beyond 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?

One concise sentence with front-loaded purpose. No extraneous words.

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 tool's simplicity, annotations, and presence of an output schema, the description is complete. It explains core functionality and similarity criteria.

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?

Schema coverage is 100% with parameter descriptions. The description adds meaning by specifying the similarity basis (category/sector), which the schema parameter descriptions do not include.

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 finds related coins based on category/sector similarity. It distinguishes from siblings like coin_history (historical data) or list_coins (all coins).

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 discovering similar coins by sector, but lacks explicit guidance on when to use this tool vs. alternatives 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.

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