Skip to main content
Glama

Market Calendar & Trading Hours

tt_market_calendar
Read-onlyIdempotent

Exchange holidays + trading hours. No setup needed beyond the one-time sign-in — no broker, paid plan, or strategy data.

from_date / to_date: YYYY-MM-DD (e.g. '2026-10-02'); any other format is refused with COMMON_BAD_INPUT. holidays.window echoes the window served. For one day, pass the same date in both. With no dates the window is today (IST) plus 90 days; a missing to_date is 90 days after from_date, a missing from_date 90 days before to_date (holidays.window.defaulted says which was filled in). For a whole year, pass that year's first and last day.

Use for "is the market open on ?", "when does NSE close?", trading-hours/timezone questions. Returns the holiday list (incl. partial-day Muhurat exceptions) and per-exchange start/end/expiry times. Also returns now (the current IST time) and, when the window covers today, today (does the exchange trade today, is it open now): answer "is the market open today?" from those, not from your own date.

Read field_note before quoting a field. Three of them are not what they look like: the holiday rows are nested at holidays.holidays; holidays.excludes is a small GLOBAL list returned unfiltered on every call (the same three rows come back for a US or crypto venue, two of them Indian Union Budget days) and is not part of the answer to the query; and expiry_time is the master's stored stamp, reading 00:00:00 on the thirteen venues that have none and not always sitting inside the row's own session. Trading hours are start_time / end_time and sessions.

For holiday-aware strategy logic (e.g. "skip to next trading day"), use the tt_next_trading_day keyword instead — it resolves at runtime.

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": "tt_market_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
to_dateNoYYYY-MM-DD. Default: 90 days after from_date.
exchangeNo
from_dateNoYYYY-MM-DD. Default: today (IST), or 90 days before to_date.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorldHint=false, yet the description still adds real context: the COMMON_BAD_INPUT error on bad date formats, the default-window rules, and the `holidays.window.defaulted` flag that reports which bound was filled in. It also warns that `holidays.excludes` is a small global list returned unfiltered on every call and that `expiry_time` is a stored master stamp reading 00:00:00 on thirteen venues, which prevents misreading results.

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?

The purpose and the sibling alternative are front-loaded, and the middle paragraph is dense with operational facts rather than filler. The closing field_note paragraph is necessarily long given how many return-shape traps it defuses, though it sprawls a little and could be tightened into shorter clauses.

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

Completeness5/5

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

There is no output schema, so the description carries the full burden of explaining returns, and it does: holiday list including partial-day Muhurat exceptions, per-exchange start/end/expiry times, `now`, and `today` with explicit instruction to answer 'is the market open today?' from those rather than from the model's own date. It even flags the three misleading fields (nested `holidays.holidays`, global `holidays.excludes`, `expiry_time`) an agent would otherwise misread.

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?

Schema coverage is 67%, and the description more than compensates on the date parameters: YYYY-MM-DD format, rejection of other formats, the same-date-in-both trick for a single day, the whole-year convention, and both default rules (no dates = today IST + 90 days; missing to_date = from_date + 90 days). The `exchange` parameter, however, is never explicitly described in either place — venue filtering is only implied by 'per-exchange' and the US/crypto aside, so no accepted format or default is given.

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?

The opening line, 'Exchange holidays + trading hours,' states a concrete verb-and-resource pair, and the examples ('is the market open on <date>?', 'when does NSE close?') pin down the exact question it answers. It also explicitly names the sibling keyword tt_next_trading_day as the different tool for holiday-aware strategy logic, so an agent can separate the two without opening either schema.

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

Usage Guidelines5/5

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

It states when to use this tool (open/closed questions, trading-hours and timezone questions) and when not to ('for holiday-aware strategy logic ... use the tt_next_trading_day keyword instead — it resolves at runtime'). It also removes a common prerequisite doubt by saying no broker, paid plan, or strategy data is needed beyond the one-time sign-in.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources