Skip to main content
Glama

FoxAPIs data sources

CoinGecko coin

coingecko_coin
Read-onlyIdempotent

Price, market cap, volume, supply and 24-hour change for a coin, by its CoinGecko id. Costs 2 credits a call; an answer with no data is not charged. Needs your FoxAPIs key (free to start).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "coin_id": "<coin_id>"
    },
    "name": "coingecko_coin"
  }
}

Input Schema

NameRequiredDescriptionDefault
coin_idYesFor example: "bitcoin"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive, so the safety profile is covered. The description adds genuinely new operational context: 2 credits per call, no charge for an empty answer, and a required FoxAPIs key. It does not mention rate limits beyond the credit cost or data freshness, keeping it below a 5.

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?

Three short sentences with no filler, front-loaded with what the agent gets, then how to identify the coin, then cost and auth. Every clause carries information an agent needs before calling.

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

Completeness4/5

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

For a single-parameter read tool with no output schema, listing the returned fields, the cost model, and the credential requirement covers nearly everything. Minor gaps: no mention of quote currency (e.g., whether values are USD) or data staleness.

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 an inline example ("bitcoin"), so the baseline is 3. The description adds real meaning by specifying a CoinGecko id rather than a ticker symbol or name, which is the most common invocation error for this class of API.

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 names the exact fields returned (price, market cap, volume, supply, 24-hour change) and the resource (a coin), plus the identifier type (CoinGecko id). That is precise enough to act on immediately. It stops short of naming any sibling, so it earns a 4 rather than a 5.

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?

Usage is implied by the narrow scope: fetch market data for one coin. There is no explicit when-to-use or when-not statement, and no alternative named (e.g., a protocol-level or multi-coin tool). The credit and key notes are helpful but are billing facts, not selection guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources