nse_get_quoteRetrieve a live NSE equity quote by trading symbol, e.g. INFY or RELIANCE, via an unofficial public endpoint.
Get a live NSE equity quote (unofficial public endpoint).
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes | NSE trading symbol, e.g. 'INFY', 'RELIANCE', 'TCS'. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations, so the description carries the full burden. 'Unofficial public endpoint' is a valuable disclosure about reliability and support, but it doesn't state whether this requires authentication, rate limits, whether quotes are delayed, or what the freshness/latency profile is. With no annotations and an output schema (which covers returns), a 3 reflects partial behavioral coverage.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, well-formed sentence that front-loads the core action and resource, with no padding. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists so return values needn't be described. However, for a real-time market-data tool with no annotations, the description omits critical context: authentication needs, rate limits, and latency/delay. The endpoint reliability note is present but incomplete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%; the single 'symbol' parameter is fully documented in the schema with examples. The description adds no parameter details beyond what the schema provides, but since there is only 1 param and schema coverage is complete, the baseline is high.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (get) and resource (live NSE equity quote), distinguishing it from nse_get_index_quote (index) and nse_get_historical (historical). The '(unofficial public endpoint)' qualifier adds useful scoping but the core purpose is clear enough to select it over siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this versus nse_get_historical (which presumably also returns quotes but at historical points) or contextual siblings. The phrase 'live' implies realtime, but no explicit when-to-use or when-not-to-use is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.