Skip to main content
Glama
cmc-market-agent

cmc-market-agent

by melatim80186

get_trending

Retrieve coins trending on CoinMarketCap now to identify current market interest. Set a limit of 1–20 coins; returns up to 10 by default.

Instructions

Coins trending on CoinMarketCap right now. Uses CMC endpoint /v1/cryptocurrency/trending/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_trending"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many coins, default 10

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does add one useful trait: the data reflects current trending status, not a historical window. It omits auth requirements, rate limits, what determines 'trending' (rank basis, time window), and the shape of returned entries.

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 sentences, front-loaded with the resource and scope before the implementation detail. The endpoint reference is marginally useful provenance but does not crowd out the core statement.

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?

For a simple single-parameter read tool with no output schema and no annotations, the description is complete enough to invoke but thin on what an entry contains and what defines trending. It leaves an agent guessing about the result structure and the ranking basis.

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% with a single optional 'limit' parameter (1-20, default 10) fully documented in the schema. The description adds nothing about the parameter, 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 a specific resource and freshness ('Coins trending on CoinMarketCap right now'), which an agent can map to a concrete retrieval operation. It does not explicitly contrast itself with siblings like get_gainers_losers, so differentiation is left to the name.

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 only implied by the phrase 'right now', which signals a real-time trending query rather than a historical or ranking-based one. There is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as get_gainers_losers or get_market_brief.

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