Skip to main content
Glama
cmc-market-agent

cmc-market-agent

by melatim80186

get_gainers_losers

Retrieve cryptocurrency gainers and losers for a chosen time period to track market momentum and identify rising or falling assets.

Instructions

Top gainers and top losers over a time period. Uses CMC endpoint /v1/cryptocurrency/trending/gainers-losers.

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_gainers_losers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many per side, default 10
time_periodNoWindow, default 24h

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 burden. It implies a read-only market data fetch and mentions the upstream endpoint, but says nothing about rate limits, data freshness/caching, or what happens when the window has sparse data. Naming the endpoint is minor context, not real behavioral disclosure.

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, purpose front-loaded with the endpoint reference trailing. Nothing is wasted, though the endpoint sentence contributes little to an agent's decision.

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 two-optional-parameter read tool with full schema coverage and no output schema, the definition is minimally adequate. It still leaves the agent without a sense of return shape, per-side limits behavior, or how it differs from get_trending.

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 both parameters documented in-schema including the default-10 per-side semantics and the 1h/24h/7d/30d enum. The description adds nothing 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?

The description states a specific verb-and-resource pair: it returns top gainers and top losers over a time period, and names the underlying CMC endpoint. It is clear about what it returns but does not differentiate itself from siblings like get_trending, which an agent might reasonably confuse with gainers/losers ranking.

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?

There is no when-to-use guidance, no exclusions, and no mention of alternatives such as get_trending or get_quote. The agent must infer that this tool is for ranked momentum lists rather than general trending or single-asset quotes.

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