Skip to main content
Glama
indian-option-mcp

indian-option-mcp

get_spot_price

Fetches the current NSE spot price for an Indian stock or index, with timestamp, so you can verify the underlying before calculating Greeks or building options strategies.

Instructions

Get the current spot/underlying price of an Indian stock or index from NSE. Use this to check the latest price before calculating Greeks or building strategies. Returns spot price with timestamp.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "get_spot_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesNSE underlying symbol, e.g. NIFTY, BANKNIFTY, RELIANCE, INFY

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, but the description discloses the return payload ("spot price with timestamp") and the data source (NSE), which is genuine behavioral information. It does not address data freshness/latency, market-closed behavior, or failure modes such as an unknown symbol, which leaves gaps for a live-market lookup 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?

Three short sentences, front-loaded with the verb and resource, then usage, then return value. No padding or restatement of the name.

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?

For a one-parameter read tool with no output schema, the description covers source, purpose, and return shape adequately. Minor gap: nothing about timeliness or behavior outside market hours, which matters for a "current" price lookup.

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

Parameters3/5

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

Schema coverage is 100% and the single `symbol` parameter already carries an NSE example set, so the schema does the heavy lifting. The description reinforces the exchange constraint (NSE only) but adds no format or validation detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Get the current spot/underlying price") plus scope (Indian stock or index, from NSE), which clearly separates it from the Greeks/strategy/payoff siblings. It stops short of naming an alternative tool, so discrimination is implied rather than explicit.

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?

"Use this to check the latest price before calculating Greeks or building strategies" gives a concrete usage context and positions it as the upstream input step in a workflow. It does not state when not to use it (e.g., for historical prices or option premiums, which other tools cover).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.