Skip to main content
Glama
indian-option-mcp

indian-option-mcp

market_status

Check if the Indian stock market (NSE) is open or closed, with trading hours, weekends, and holiday coverage, before placing trades or explaining stale data.

Instructions

Check if the Indian stock market (NSE) is currently open or closed. Returns market status with trading hours info. Use before placing trades or to explain why data may be stale. Accounts for weekends and Indian market holidays.

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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose the key behavioral traits: it accounts for weekends and Indian market holidays, and it warns that stale data may be explained by closure. It implies a read-only, side-effect-free check but never states the exact returned fields beyond 'market status with trading hours info'.

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?

Three compact sentences, front-loaded with the core purpose and followed by return value and edge-case handling. The phrase 'Returns market status with trading hours info' slightly restates the opening sentence but earns its place by hinting at the payload.

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 simple zero-parameter read tool with no output schema, the definition covers purpose, return content, and the holiday/weekend logic that drives the result. Only the concrete shape of the response (field names, timezone or timestamp format) is left unspecified, which is a minor gap.

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 no parameters, so there is nothing for the schema to document and the baseline is a 4. The description correctly implies the call needs no input and returns a status derived from server-side date and holiday rules.

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?

States a specific verb and resource ('Check if the Indian stock market (NSE) is currently open or closed') and scopes it to NSE, which cleanly separates it from siblings like market_overview that return data rather than a status flag. An agent can pick it without opening any schema.

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?

Gives explicit when-to-use guidance: 'Use before placing trades or to explain why data may be stale.' It does not name a when-not condition or an alternative tool, but for a zero-parameter status check there is little ambiguity about alternatives.

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