Skip to main content
Glama
tanmaymish

MarketPulse MCP

by tanmaymish

nse_top_movers

Identify today's top-performing NSE stocks. Get gainers, losers, or most-traded stocks from Nifty 50 to spot market trends.

Instructions

Get today's top performing stocks on NSE.

Returns the top 10 stocks by the specified criteria from Nifty 50 components.

Args: mover_type: Type of movers to fetch. Options: - gainers: Top 10 stocks with highest % gain today - losers: Top 10 stocks with highest % loss today - active: Top 10 stocks by trading volume

Examples: nse_top_movers("gainers") → Today's top gainers nse_top_movers("losers") → Today's top losers nse_top_movers("active") → Most actively traded stocks

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mover_typeNogainers

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses important behavioral traits: it is limited to Nifty 50 components, returns exactly top 10 stocks, and uses 'today's' performance (implying time-sensitivity). It doesn't cover edge cases like market holidays or after-hours behavior, but for a simple read tool it is fairly transparent.

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 well-structured and front-loaded with the core purpose. It uses short sections (Args, Examples) and every sentence adds value. It is informative without being verbose.

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

Completeness5/5

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

For a simple one-parameter tool, the description is complete. It explains the parameter options, gives examples, and clarifies the Nifty 50 scope and top-10 limit. The output schema exists, so detailed return values are not needed in the description.

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

Parameters5/5

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

The input schema has one parameter with no description (0% coverage), but the description fully compensates by explaining the three accepted values (gainers, losers, active) and what each returns. The examples also clarify the expected input format. This adds significant meaning beyond the schema.

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: 'Get today's top performing stocks on NSE' and specifies it returns the top 10 stocks from Nifty 50 components. This is a specific verb+resource+scope, and it distinguishes itself from sibling tools like nse_quote or nse_market_status.

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 tool's usage is clearly implied through examples ('nse_top_movers("gainers") → Today's top gainers') and the description of the mover_type options. However, it does not explicitly mention when to use this tool over alternatives or any exclusions, so it lacks direct sibling differentiation.

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/tanmaymish/MarketPulse-MCP'

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