Skip to main content
Glama

CryptoData API

by io.github.elevasyncsolutions-jpg

get_coin

Detailed coin info: price, ATH, supply, categories, social (api_key required).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
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",
-  "id"
-]New value: +[
+  "id"
+]
  3. Changed2 schema fields changed
    • removedInput schema / properties / api_key / description
      Removed value: -"Your API key"
    • removedInput schema / properties / id / description
      Removed value: -"Coin ID (e.g. bitcoin, ethereum)"
  4. First observed

TDQS

C2.8/5.0
Behavior2/5

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

No annotations exist, so description must disclose behavior. It mentions api_key requirement for social data, but doesn't describe rate limits, error handling, or what happens without api_key for other fields. Schema already notes api_key parameter, so description adds minimal transparency.

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?

Single sentence with clear front-loading ('Detailed coin info'). Lists specific fields concisely. No wasted words, but could be more structured (e.g., bullet points).

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?

No output schema, but description lists return fields. Missing details on data freshness, pagination, or structure. Adequate for a simple tool but incomplete for complex data like price history or social stats.

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?

Schema coverage is 50% (only api_key has a description). The description adds no meaning for the 'id' parameter (no format or source) and only reiterates api_key's role. Users must infer what 'id' refers to.

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?

Description clearly states it provides 'detailed coin info' listing specific data fields (price, ATH, supply, categories, social). This differentiates from simpler tools like get_price or get_summary, though could be more explicit about the coin identification (ID vs name).

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 explicit guidance on when to use this tool vs siblings. The note 'api_key required for social' is the only usage hint, but no when/when-not context is provided.

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