Skip to main content
Glama
indian-option-mcp

indian-option-mcp

market_overview

Fetches current NIFTY and BANKNIFTY index values plus key options data to provide a quick overview of Indian market conditions.

Instructions

Get a comprehensive overview of Indian market indices — NIFTY, BANKNIFTY with current values and key options data.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "market_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose the returned content ('current values and key options data') for the named indices. However, it omits whether data is real-time or delayed, what happens outside market hours, whether errors occur when markets are closed, and what 'key options data' concretely includes.

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?

A single front-loaded sentence with no filler, and the resource and payload scope come early. 'Comprehensive' and 'key options data' are slightly vague qualifiers that could be tightened into concrete field names.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-argument snapshot tool with no output schema, the description is minimal but serviceable. It still leaves the agent guessing about data freshness, market-hours behavior, and the exact contents of the 'key options data' portion, which matters for deciding whether to trust this as a single source.

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 tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. The description does implicitly confirm no input is required, consistent with the empty object 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 ('Get') and resource ('overview of Indian market indices'), and names the concrete subjects (NIFTY, BANKNIFTY) plus the payload scope ('current values and key options data'). An agent can tell this is a broad index snapshot rather than a single-value lookup, though the description never explicitly contrasts it with close siblings like get_spot_price or market_status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this versus alternatives, and no prerequisites or exclusions. Usage is only implied by the word 'overview' — an agent must infer that this is a broad first-look call before drilling into get_option_chain or get_spot_price.

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