Skip to main content
Glama
Sign In
polygon-mcp

polygon-mcp

by atomcp-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

crypto_get_gainers_and_losers

Identify the top 20 cryptocurrency gainers or losers. Track significant price movements to analyze market trends and momentum.

Instructions

Get top 20 crypto gainers or 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": "crypto_get_gainers_and_losers"
  }
}

Input Schema

NameRequiredDescriptionDefault
directionNogainers

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral details. It reveals the retrieval limit (top 20) but fails to mention that the operation is read-only, that 'direction' defaults to 'gainers', or what data points are included in the response. This is a sparse disclosure for an unannotated tool.

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?

The description is a single concise sentence, front-loaded with the verb 'Get'. It contains no filler and is appropriately sized for a simple tool, though brevity comes at the cost of omitted details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is insufficiently complete. It does not explain how to select between gainers and losers, what the default is, or what fields the returned items contain. For a tool with one parameter, this is a clear gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has a single 'direction' parameter with no description and no enum. The description mentions 'gainers or losers' but does not explicitly link this to the 'direction' parameter or specify the exact valid values. With 0% schema description coverage, the description fails to adequately explain the parameter's meaning and default behavior.

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 tool's function: to retrieve the top 20 crypto gainers or losers. It names the resource (crypto market) and scope (top 20), and distinguishes it from sibling tools for stocks and forex by including 'crypto'.

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?

The description provides no guidance on when to use this tool compared to alternatives such as stocks_get_gainers_and_losers or other crypto indicators. It does not mention prerequisites, exclusions, or context for choosing this over similar tools.

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

Deploy Server

Other Tools