crypto_gainers
Identify the top-performing cryptocurrencies by price increase to spot market movers and potential investment opportunities.
Instructions
Get top crypto gainers
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Identify the top-performing cryptocurrencies by price increase to spot market movers and potential investment opportunities.
Get top crypto gainers
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations, and the description only says 'Get top crypto gainers'. It does not disclose what the tool returns (list format, number of results, sorting criteria), any limitations, or whether it is a read-only operation. The description carries the full burden and fails to provide meaningful behavior beyond the action.
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?
The description is a single short sentence with no redundancy. It is concise and front-loaded with the core action. While it omits key context, conciseness itself is excellent.
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?
Given the simple nature (no parameters, no output schema), the description still leaves questions: what defines 'top' gainers, what time frame, what data is returned? With no annotations or output schema, the description should clarify these aspects. It does not, making it incomplete for an agent to predict the tool's behavior.
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 tool has zero parameters, and per the instructions the baseline is 4. The description does not need to explain parameters that don't exist, and the schema covers all parameters trivially.
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?
The description states a clear verb 'Get' and resource 'top crypto gainers', and the asset class 'crypto' distinguishes it from sibling tools like stocks_gainers and forex_gainers. However, it does not specify how 'top' is defined (e.g., time period or ranking metric), which is a minor gap.
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?
The description provides no guidance on when to use this tool versus its siblings. There is no mention of alternatives like crypto_losers or stocks_gainers, nor any conditions for selecting this tool. An agent must infer from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/axionquant/mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server