Skip to main content
Glama

Coinmarketcap Category

coinmarketcap_category
Read-onlyIdempotent

Fetch all coins belonging to a CoinMarketCap category (e.g. DeFi, NFTs) by category id (obtain ids from the categories tool); returns price, market cap, and 24h change per coin.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "defi"
    },
    "name": "coinmarketcap_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCategory id (from `categories`)
convertNo

Output Schema

NameRequiredDescriptionDefault
dataNo
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds meaningful behavior beyond that: the two-step dependency on `categories` for ids and the per-coin payload (price, market cap, 24h change). Pagination, rate limits, and result caps are not mentioned.

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?

One sentence, front-loaded with purpose, then the id-source prerequisite, then the returned fields. The parentheticals are load-bearing rather than decorative, and there is no redundant restatement of annotations.

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?

With an output schema present, the return-value explanation is technically redundant but harmless, and the id-sourcing guidance is exactly what an agent needs before calling. The only missing piece is any explanation of `convert`, which is the remaining ambiguity for a two-parameter call.

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 50%: `id` is documented in the schema and the description reinforces it with examples and the `categories` pointer. The `convert` parameter is undocumented in both the schema and the description, so an agent must infer that it means currency conversion; this is a real gap the description does not close.

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?

States a specific verb and resource ('Fetch all coins belonging to a CoinMarketCap category') and bounds the scope to a single category id, with concrete examples (DeFi, NFTs). It also names the sibling `categories` tool as the id source, so an agent can place it in the workflow without opening any schema.

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

Usage Guidelines4/5

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

Gives an explicit prerequisite: category ids must be obtained from the `categories` tool, which tells the agent when this tool is applicable and what must happen first. It does not state exclusions (e.g. when to use `coinmarketcap_quotes` instead for a known coin list), keeping it short of a 5.

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.