Skip to main content
Glama
cmc-market-agent

cmc-market-agent

by melatim80186

get_listings

Retrieve top cryptocurrencies ranked by market cap with configurable count and fiat conversion to answer crypto market ranking questions.

Instructions

Top cryptocurrencies ranked by market cap. Uses CMC endpoint /v1/cryptocurrency/listings/latest.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many coins, default 10
convertNoFiat currency, default USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It notes the upstream CMC endpoint and implies a 'latest' snapshot, but says nothing about the read-only nature of the call, rate limits, caching/staleness, or whether limit is capped — all things an agent would want before calling.

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?

Two short, front-loaded sentences with no filler; the purpose is stated first and the endpoint detail second. The endpoint reference is of marginal value to an agent but is not wasteful enough to penalize.

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 simple two-optional-parameter read tool with no output schema, the description is adequate: it establishes the ranked list and its data source. It could optionally hint at what fields come back (price, market cap, volume), but nothing needed to invoke it correctly is missing.

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 description coverage is 100%, with limit and convert fully documented in the schema itself, including defaults. The description adds no additional parameter meaning beyond the schema, so the baseline 3 applies.

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?

States the resource and ordering concretely: 'Top cryptocurrencies ranked by market cap', which tells an agent exactly what the returned list represents. It does not contrast with siblings such as get_trending or get_gainers_losers, so an agent must infer when the market-cap ranking is the right view.

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 when-to-use or when-not-to-use guidance and no named alternatives. The agent must decide on its own whether a ranked market-cap listing or a trending/movers/quote tool better fits the request.

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