Skip to main content
Glama

TradeTi.me — Market Hours

get_exchange_status

Read-onlyIdempotent

Full live status for one exchange: open flag, status enum (main_open / session_open / opening_soon / closed), session type, hours to the next transition, hours to close (if open), and why it is closed (holiday / weekend) if applicable. When a 2027 holiday or early close drives the result, calendarStatus and holidayStatus are official or estimated. estimated means the exchange has not published that date yet; it was derived from the exchange's own past calendar and may change.

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": {
      "exchange": "<exchange>"
    },
    "name": "get_exchange_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNoOptional ISO 8601 timestamp to evaluate AT a specific moment (e.g. "2026-07-06T14:30:00Z"). Defaults to now. Use it for "will the NYSE be open at 3pm ET on Monday?".
exchangeYesExchange id (e.g. "nyse", "nasdaq", "lse", "nikkei", "hkex") OR common name/city (e.g. "New York Stock Exchange", "Tokyo", "London"). Case-insensitive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, non-open-world behavior, so the description is free to add data-provenance context instead, which it does: it explains that calendarStatus/holidayStatus can be 'official' or 'estimated', that 'estimated' means the exchange has not yet published the date, and that the value is derived from past calendars and may change. That is a meaningful disclosure an agent cannot get from annotations or schema.

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?

Two dense sentences, front-loaded with the capability before the estimation caveat. The second sentence is long but each clause explains real semantics (official vs estimated, why estimated may change), so little is wasted.

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?

There is no output schema, and the description compensates by enumerating the return fields including the status enum values and the closure-reason values. It also explains the estimation caveat. What is missing is behavior on an unresolvable exchange id or a mixed case, but for a two-parameter read tool this is close to complete.

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 description coverage is 100%, and the schema already explains both 'exchange' (ids or common names/cities, case-insensitive) and 'at' (ISO 8601, defaults to now, with a worked example). The description adds no parameter-level meaning beyond what the schema states, so the baseline of 3 applies.

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?

The description gives a specific verb and resource ("Full live status for one exchange") and enumerates the returned fields: open flag, status enum values, session type, hours to transition, hours to close, and closure reason. This clearly separates it from boolean siblings like is_market_open or markets_open_now, though it never names an alternative explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: the enumerated payload suggests this is the richer counterpart to is_market_open, and the 'at' parameter description carries the one concrete scenario ("will the NYSE be open at 3pm ET on Monday?"). There is no stated when-not-to-use or direct referral to a sibling.

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