Skip to main content
Glama

CryptoData API

by io.github.elevasyncsolutions-jpg

get_exchanges

Exchange listings: volume, trust score, country (api_key required).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
api_keyNoYour API key from register()

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedInput schema / properties / api_key / description
      Previous value: -"Optional — for billing"New value: +"Your API key from register()"
  2. Changed2 schema fields changed
    • addedInput schema / properties / api_key / description
      Added value: +"Optional — for billing"
    • changedInput schema / required
      Previous value: -[
-  "api_key"
-]New value: +[]
  3. Added

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations provided, the description must fully disclose behavioral traits. It mentions the api_key requirement, but fails to indicate that the tool is read-only, has rate limits, or any other behavioral aspects. The description is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise—one short sentence with core information front-loaded. However, it could benefit from slight expansion to cover essential details like return values. Still, efficiency is high.

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

Completeness2/5

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

Given the tool has no output schema, the description should at least hint at the return format or data structure. It does not. Also, no behavioral context beyond api_key is provided. For a 2-parameter tool, it is minimally complete but lacks depth.

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

Parameters2/5

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

The description adds some value by indicating 'api_key required', which implies auth is needed despite the schema not marking it as required. This is useful but contradictory to the schema's 'required: []'. The other parameter 'limit' is not discussed. Schema coverage is 50%, but the description only partially compensates.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists exchanges with volume, trust score, and country. The verb 'listings' is clear and the resource 'exchanges' is explicit. However, it does not differentiate from other get_* tools in the sibling list, though the name itself is distinctive enough.

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?

The description only mentions 'api_key required' as a condition, but provides no guidance on when to use this tool versus alternatives like get_search or get_top. No context on prerequisites or scenarios is given.

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

All CryptoData API toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.8/5.0
Disambiguation4/5

Tools generally have distinct purposes, but some overlap exists between price history tools (get_ohlc vs get_price_summary) and meme-related tools (analyze vs scan vs trending). Overall, descriptions help differentiate.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern (e.g., get_price, set_price_alert, analyze_contract). No mixing of conventions.

Tool Count3/5

48 tools is on the higher side, but it covers a broad spectrum of crypto data (prices, DeFi, sentiment, alerts, etc.) and each tool seems justified. However, the count could be slimmed down by grouping similar functions.

Completeness4/5

Very comprehensive coverage of crypto data: prices, market stats, DeFi, sentiment, gas, alerts, portfolio, arbitrage, token analysis. Minor gaps like NFT data or direct exchange rate queries.

Resources