mcp-server

Get coin metadata

get_coin

Read-onlyIdempotent

Full metadata for a coin: description, links, categories, market data, developer stats.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`coinId`	Yes	Canonical coin id or slug (e.g. "bitcoin")

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Canonical coin ID (e.g. `bitcoin`)
`name`	Yes	Human-readable name (e.g. `Bitcoin`)
`rank`	No	Market cap rank (1 = largest)
`price`	No	Current spot price in USD
`symbol`	Yes	Trading symbol (e.g. `btc`)
`marketCap`	No	Market cap in USD

Schema Changelog

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

Changed1 schema field changedMay 21, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "id": {
+      "description": "Canonical coin ID (e.g. `bitcoin`)",
+      "type": "string"
+    },
+    "marketCap": {
+      "description": "Market cap in USD",
+      "type": "number"
+    },
+    "name": {
+      "description": "Human-readable name (e.g. `Bitcoin`)",
+      "type": "string"
+    },
+    "price": {
+      "description": "Current spot price in USD",
+      "type": "number"
+    },
+    "rank": {
+      "description": "Market cap rank (1 = largest)",
+      "type": "integer"
+    },
+    "symbol": {
+      "description": "Trading symbol (e.g. `btc`)",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "symbol",
+    "name"
+  ],
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, indicating a safe read operation. The description adds value by detailing the exact attributes returned, which goes beyond annotations without contradiction.

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?

The description is two sentences long, front-loaded with the purpose, and contains no redundant information. Every phrase adds value.

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 output schema exists (not shown but referenced), the description covers the key return fields. For a metadata retrieval tool with one parameter, the description is complete.

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 the single parameter coinId, with a clear description. The tool description does not add additional semantics beyond what the schema provides, so baseline 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?

The description clearly states the tool returns 'Full metadata for a coin' and specifies contents: description, links, categories, market data, developer stats. This distinguishes it from siblings like get_price (price only) or list_coins (list only).

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 comprehensive metadata but does not explicitly state when to use this tool versus alternatives such as get_price for price-only queries. No exclusions or context are provided.

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

All mcp-server tools Inspect

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

A3.9/5.0

Disambiguation5/5

Each tool targets a distinct aspect of cryptocurrency data: coin metadata, prices, rates (current, historical, changes), earn products, market summaries, stablecoin analysis, and symbol resolution. The detailed descriptions clearly differentiate even similar tools like get_price and get_price_by_symbol, or get_rates and list_earn_products.

Naming Consistency3/5

All names use snake_case, but conventions vary: some are verb_noun (get_coin, list_coins, resolve_symbol), some are noun_noun (coin_history, fear_greed_index, market_summary), and some include 'by' for parameters. This mix is readable but could be more consistent.

Tool Count5/5

With 21 tools, the server covers a broad domain of cryptocurrency data without being overwhelming. Each tool serves a clear purpose, and the count is appropriate for a comprehensive data API.

Completeness5/5

The tool set covers nearly all expected operations for a crypto data server: coin listing, metadata, prices, historical data, rates, yield products, market stats, top coins, stablecoin analysis, and symbol resolution. No obvious gaps are present for the stated focus on price, rate, and yield data.

Resources

Need Help?