Retrieve current aggregate crypto-market metrics, including market capitalization, volume, and dominance, to assess overall market conditions. Supports currency conversion.
Get CoinMarketCap's latest aggregate crypto-market metrics, including market capitalization, volume, and dominance measures.
| Name | Required | Description | Default |
|---|---|---|---|
| convert | No |
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | ||
| status | Yes |
Changes observed during successful MCP inspections.
v1.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral burden. 'Get' implies read-only behavior and 'latest' implies freshness, but auth requirements, rate limits, and any safety constraints are unstated.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no wasted words. It is appropriately sized for a simple metrics-fetching tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values do not need to be explained. However, for a tool with no annotations and an undocumented 'convert' parameter, the description still leaves clear gaps around how to call it and when to prefer it over sibling endpoints.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single 'convert' parameter is entirely absent from the description. Schema description coverage is 0%, and the description does not explain that the parameter controls currency conversion or any of its constraints.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Get') and resource ('CoinMarketCap's latest aggregate crypto-market metrics'), and lists the included data families. It implicitly distinguishes itself from asset-level siblings via 'aggregate', but it does not name or contrast any sibling tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit when-to-use or when-not-to-use guidance is given. 'Latest' hints at current-snapshot usage versus historical siblings, but no alternatives or conditions are stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.