Skip to main content
Glama

nse_quarterly_results

Retrieve quarterly financial results for NSE stocks showing revenue, profit, EPS, EBITDA, and quarter-over-quarter growth for the last four quarters.

Instructions

Get latest quarterly financial results for an NSE stock.

Shows revenue, profit, EPS, EBITDA for last 4 quarters with quarter-over-quarter growth rates.

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

Examples: nse_quarterly_results("RELIANCE") → Reliance Q results nse_quarterly_results("TCS") → TCS quarterly financials

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided; description lacks disclosure of data freshness, API limits, or source. Only states output fields, not behavioral traits. Relies on minimal description for a read-only tool.

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?

Very concise: short summary, bullet list of metrics, args, examples. No waste, front-loaded with key info. Earns every sentence.

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?

Covers purpose, param, and output fields. Output schema exists but description doesn't detail structure; however, tool is simple and listed fields are sufficient for understanding.

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?

Single parameter 'symbol' well-explained with examples (RELIANCE, TCS) in description, compensating for 0% schema description coverage. Adds meaning beyond 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?

Clearly states it gets latest quarterly results for NSE stocks, lists specific financial metrics (revenue, profit, EPS, EBITDA) with growth rates. Distinguishes from siblings like nse_quote or stock_historical by specifying financial results.

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?

Implies it's for quarterly results but does not explicitly contrast with alternatives like nse_historical or income_statement. No when-not or alternative tool mentions, leaving room for ambiguity.

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