Skip to main content
Glama
Akhilgovind02

india-stock-mcp

get_gainers_losers

Fetch top gainers or losers among NIFTY 50 stocks, ranked by percentage change from live quotes. Specify the type (gainers or losers) and number of stocks to return.

Instructions

Get top gainers or losers among NIFTY 50 stocks, ranked by % change (live Yahoo quotes).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesWhether to get top gainers or top losers
countNoHow many stocks to return
Behavior3/5

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

Discloses data source (live Yahoo quotes) and ranking basis (% change), but lacks details on update frequency, reliability, rate limits, or authentication needs. No annotations provided, so description carries full burden.

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?

One clear, front-loaded sentence with no redundant information. Every word adds value.

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

Completeness3/5

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

Missing output format description (e.g., list of stocks with symbol, % change), especially since no output schema exists. Also lacks mention that data is live and changes per call.

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

Parameters3/5

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

Schema descriptions already fully cover both parameters (type enum, count numeric). The description adds 'ranked by % change' but this is about output, not parameter semantics.

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?

Clearly states the tool retrieves top gainers or losers from NIFTY 50 stocks ranked by % change using live Yahoo quotes. This specific verb-resource combination distinguishes it from sibling tools like get_quote or compare_stocks.

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

Usage Guidelines3/5

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

Implied usage when needing top movers, but no explicit when-to-use or when-not-to-use guidance. Does not contrast with similar tools like get_quote that could provide individual stock data.

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/Akhilgovind02/india-stock-mcp'

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