Skip to main content
Glama

live_quote

Fetch live NSE quotes for stocks or indices, including last traded price, OHLC, volume, average price, circuit limits, buy/sell quantity, and 52-week range. Requires Angel One API credentials.

Instructions

Real-time NSE quote via Angel One SmartAPI — zero delay, no yfinance lag.

Requires Angel One API credentials in your .env file (stays local, never on GitHub). Falls back gracefully if not configured, with setup instructions.

Zerodha Kite Connect charges ₹500/month for real-time data API. Angel One SmartAPI is free for account holders.

Provides (when configured):

  • Live Last Traded Price (LTP) — real-time, zero delay

  • OHLC for the day

  • Volume, average price

  • Upper/lower circuit limits

  • Buy/sell quantity

  • 52-week high/low

Setup (one-time): Add to .env: ANGEL_API_KEY, ANGEL_CLIENT_ID, ANGEL_PASSWORD, ANGEL_TOTP_SECRET pip install finstack-mcp[broker]

Args: symbol: NSE symbol (e.g., RELIANCE, TCS, NIFTY, BANKNIFTY)

Examples: live_quote("RELIANCE") → Real-time Reliance price (if Angel One configured) live_quote("NIFTY") → Live Nifty index price

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: requires Angel One API credentials stored locally, real-time zero-delay data, graceful fallback, and the full set of returned fields (OHLC, volume, circuit limits, etc.). No contradictions.

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

Conciseness4/5

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

The description is detailed but well-structured with a summary line, bullet points for features, setup steps, and examples. It is slightly verbose but every section adds value; no redundant fluff.

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?

The description covers purpose, required credentials, fallback behavior, data fields, and examples. While no formal output schema is referenced, the list of provided fields suffices. It lacks explicit mention of pagination or rate limits, but for a single-parameter quote tool, it is largely complete.

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?

The only parameter, 'symbol', is described as 'NSE symbol (e.g., RELIANCE, TCS, NIFTY, BANKNIFTY)', providing concrete examples and implying support for both stocks and indices. This adds meaning beyond the schema's type and title, though the schema has 0% coverage.

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 it provides real-time NSE quotes via Angel One SmartAPI, explicitly listing the data fields (LTP, OHLC, volume, etc.). It distinguishes itself from sibling tools like bse_quote, nse_quote, and fyers_live_quote by specifying the broker and real-time nature.

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 provides setup instructions and notes that it falls back gracefully with guidance. It compares pricing with Zerodha. However, it does not explicitly advise when to use this over other quote tools in the sibling list (e.g., bse_quote, fyers_live_quote), leaving the agent to infer based on broker preference.

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