Skip to main content
Glama
atomcp-ai

polygon-mcp

by atomcp-ai

stocks_get_rsi

Compute the Relative Strength Index (RSI) for any stock symbol to assess momentum and identify overbought or oversold conditions.

Instructions

Get Relative Strength Index for a stock symbol.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
orderNodesc
symbolYes
adjustedNo
timespanNoday
timestampNo
series_typeNoclose
window_sizeNo
Behavior1/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It simply says 'Get RSI' without explaining output format, calculation period, data source, or any side effects. This is a minimal disclosure that fails to inform the agent about the tool's actual behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, which is concise but drastically under-specified. It lacks any structure or additional detail, making it more of an under-specification than a well-crafted concise description.

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

Completeness1/5

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

Given 8 parameters, no output schema, and a wide set of sibling indicators, the description is wholly incomplete. It provides no information about return values, parameter impacts, or selection criteria, leaving a large gap in context for an AI agent.

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

Parameters1/5

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

The schema exposes 8 parameters with no descriptions, and the tool description mentions none of them. There is zero compensation for the 0% schema description coverage, leaving the agent without any understanding of how parameters like limit, timespan, or window_size affect the result.

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 retrieves the Relative Strength Index for a stock symbol, using a specific verb and resource. It distinguishes from sibling RSI tools for forex, crypto, and options by limiting to stocks, and from other stock indicators by naming RSI explicitly.

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 guidance is provided on when to use this tool versus alternatives like stocks_get_ema or stocks_get_sma. The description only implies use when a stock RSI is needed, but does not mention any exclusions or comparative context.

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/atomcp-ai/polygon-mcp'

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