Skip to main content
Glama

market_coingecko_exchanges

Retrieve cryptocurrency exchanges ranked by trust score, with trading volume data per exchange. Adjust page and perPage to paginate through results.

Instructions

Get all exchanges ranked by trust score with trading volume data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number
perPageNoResults per page (1-250)
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the data returned but fails to disclose pagination behavior, rate limits, or that 'all exchanges' may require multiple pages, which is a significant omission for a paginated tool.

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, front-loaded with the tool's core function. No unnecessary words or repetition, achieving high information density.

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

Completeness3/5

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

The description is adequate for a simple list tool, but it omits pagination semantics and return format. With no output schema and no annotations, more detail would be expected to fully distinguish this from similar exchange-list tools.

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% for both parameters (page, perPage), and the description adds no additional parameter semantics. This is the baseline score when the schema fully documents parameters.

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?

Description uses a specific verb ('Get') with resource ('all exchanges') and clear qualifiers ('ranked by trust score with trading volume data'). It clearly distinguishes itself from the singular market_coingecko_exchange tool by specifying 'all exchanges'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given on when to use this tool vs. alternatives like market_get_exchanges or market_coingecko_exchange. The usage context is only implied by the description, with no explicit exclusions or alternative recommendations.

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/nirholas/universal-crypto-mcp'

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