Skip to main content
Glama
yyordanov-tradu

stock-scanner-mcp

crypto_top_gainers

Read-only

Identify top gaining cryptocurrency pairs by percentage change, filtered by exchange and minimum volume, using real-time market data.

Instructions

Get top gaining cryptocurrency pairs by percentage change. Defaults to major exchanges and volume > $10k.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
exchangeNoSpecific exchange (e.g. BINANCE)
limitNoNumber of results (default: 20, max: 50)
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows it's a safe read operation. The description adds behavioral context (defaults to major exchanges, volume > $10k). No contradictory or missing critical behaviors noted.

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?

Single sentence, no wasted words. Information is front-loaded and clear. Every part of the description serves a purpose.

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 simple read-only tool with two optional parameters, the description is largely complete. It explains defaults and filtering. Missing output format details are acceptable given the tool's straightforward nature and lack of output schema.

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?

Input schema covers 100% of parameters with descriptions. The description adds value by stating the volume filter and default exchange, which are not explicit in the schema. This supplements the schema without duplicating it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Get' and resource 'top gaining cryptocurrency pairs by percentage change'. It differentiates from sibling tools like tradingview_top_gainers (for stocks) by specifying cryptocurrency and default filters (major exchanges, volume > $10k).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides context on when to use: for crypto top gainers with default exchange and volume filters. It implies usage via defaults but does not explicitly state when not to use or alternative tools. Sibling differentiation is clear from the name and description.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yyordanov-tradu/stock-scanner-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server