Skip to main content
Glama

nse_quote

Retrieve real-time stock quotes from the National Stock Exchange of India, including price, volume, market cap, and key financial ratios.

Instructions

Get real-time NSE (National Stock Exchange) quote for an Indian stock.

Returns current price, change, volume, market cap, P/E ratio, 52-week range, sector, and more.

Args: symbol: NSE stock symbol (e.g., RELIANCE, TCS, INFY, HDFCBANK, SBIN, ITC)

Examples: nse_quote("RELIANCE") → Reliance Industries live price & stats nse_quote("TCS") → TCS live price & stats nse_quote("HDFCBANK") → HDFC Bank live price & stats

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so description carries full burden. It lists output fields but does not disclose behavioral traits like rate limits, authentication needs, or error handling for invalid symbols.

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?

Description is concise, front-loaded with purpose, lists key return items, then includes Args and Examples efficiently with no wasted words.

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?

Given the simple parameter and presence of output schema, the description is mostly complete. It lists return fields and examples, though it could add notes on error cases or rate limits.

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?

Schema coverage is 0% but description adds examples and specifies the format ('NSE stock symbol, e.g., RELIANCE'), providing clarity beyond the schema's vague 'string' type.

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 'Get real-time NSE quote for an Indian stock' and lists specific data points (price, change, volume, etc.). It distinguishes from siblings like bse_quote by specifying NSE.

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?

The description implies when to use (for NSE stock quotes) but does not explicitly guide when not to use or contrast with siblings like live_quote, stock_quote, or bse_quote.

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/finstacklabs/finstack-mcp'

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