Skip to main content
Glama
JackSmack1971

coinmarketcap-keyless-mcp

cmc_altcoin_season_latest

Retrieve the current CoinMarketCap Altcoin Season Index snapshot to check if altcoins are outperforming Bitcoin.

Instructions

Get the latest CoinMarketCap Altcoin Season Index snapshot.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state whether the result is a point-in-time read, how fresh the snapshot is, refresh cadence, rate limits, or what the snapshot contains. 'Snapshot' hints at a read-only point-in-time value but adds little substantive behavioral context.

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?

A single front-loaded sentence with no filler. Every word (latest, snapshot, Altcoin Season Index) carries meaning and nothing is wasted.

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 zero-parameter tool with a rich output schema already present, the description need not explain return values. It adequately establishes what is fetched; the only missing piece is routing guidance to the historical sibling. Given the output schema exists, this is nearly complete.

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?

The tool takes zero parameters, so the baseline is 4. There is nothing for the description to compensate for, and the absence of any param discussion is appropriate.

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 verb+resource: 'Get the latest CoinMarketCap Altcoin Season Index snapshot'. The 'latest' and 'snapshot' framing distinguishes it from cmc_altcoin_season_historical, though the description does not explicitly name that sibling or contrast it. Sibling differentiation is implied by 'latest' but not made explicit.

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 guidance, no exclusion of alternatives, no mention of when to prefer the historical sibling. The word 'latest' implicitly signals a current-value query, but nothing tells an agent when this rather than cmc_altcoin_season_historical is appropriate.

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