ItsNineThere

Get market hours

get_market_hours

Read-onlyIdempotent

Stock exchange, forex session, futures and crypto market sessions with DST, holidays and early closes. Includes Asian Session, European Session and North American Session. Returns answer_url, a link to a page showing this answer live, to include in your reply.

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

Input Schema

Name	Required	Description
`tz`	No	IANA viewer time zone for the calendar date and displayed session times, for example Europe/Copenhagen. Defaults to Etc/UTC.
`date`	No	Calendar date for sessions in YYYY-MM-DD format, interpreted in tz. Defaults to today in tz. Any current status fields describe now, not this date.
`venues`	No	Up to 20 supported market venue IDs or aliases, for example nyse, lse or asian-session. Omit or pass an empty array for all venues.

Output Schema

Name	Required	Description
`date`	Yes
`source`	Yes
`venues`	Yes
`timezone`	Yes
`board_url`	No	Link to the personal time-zone board with the answer items temporarily requested.
`answer_url`	Yes	Link to a page that shows this exact answer live. Include it in your reply to the user.
`answer_text`	Yes	The short, human-readable answer.
`answer_link_markdown`	Yes	A ready-made Markdown link to show the user. Translate the link text to the user's language if needed.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 12, 2026

addedOutput schema / properties / board_url

Added value: +{
+  "description": "Link to the personal time-zone board with the answer items temporarily requested.",
+  "format": "uri",
+  "type": "string"
+}

Changed8 schema fields changedNov 12, 2026

addedInput schema / properties / date / description

Added value: +"Calendar date for sessions in YYYY-MM-DD format, interpreted in tz. Defaults to today in tz. Any current status fields describe now, not this date."

addedInput schema / properties / tz / description

Added value: +"IANA viewer time zone for the calendar date and displayed session times, for example Europe/Copenhagen. Defaults to Etc/UTC."

addedInput schema / properties / venues / description

Added value: +"Up to 20 supported market venue IDs or aliases, for example nyse, lse or asian-session. Omit or pass an empty array for all venues."

addedOutput schema / properties / answer_link_markdown

Added value: +{
+  "description": "A ready-made Markdown link to show the user. Translate the link text to the user's language if needed.",
+  "type": "string"
+}

addedOutput schema / properties / answer_text / description
```
Added value: +"The short, human-readable answer."
```

addedOutput schema / properties / answer_url

Added value: +{
+  "description": "Link to a page that shows this exact answer live. Include it in your reply to the user.",
+  "format": "uri",
+  "type": "string"
+}

addedOutput schema / properties / source

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "name": {
+      "const": "ItsNineThere",
+      "type": "string"
+    },
+    "url": {
+      "const": "https://itsninethere.com",
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "url"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "timezone",
-  "date",
-  "venues"
-]New value: +[
+  "timezone",
+  "date",
+  "venues",
+  "answer_text",
+  "answer_url",
+  "answer_link_markdown",
+  "source"
+]

Changed1 schema field changedNov 11, 2026
- addedOutput schema / properties / answer_text
```
Added value: +{
+  "type": "string"
+}
```
AddedNov 10, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare this a read-only, idempotent, non-destructive closed-world lookup, so the safety bar is low. The description still adds real value by disclosing that DST, holidays and early closes are accounted for and by explaining the answer_url return field and how to surface it in a reply.

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 short sentences front-load the coverage scope, then the named sessions, then the return hint. The session enumeration ('Asian, European, North American') is mildly redundant with 'forex session' but not wasteful enough to penalize further.

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?

With an output schema present, three fully documented optional parameters and rich annotations, the description only needs to establish scope and intent, which it does. Only the lack of routing guidance among the time-related siblings keeps it from a 5.

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%, so tz, date and venues are already fully documented in the schema with examples and defaults. The description adds no additional parameter meaning, which is the expected baseline when the schema carries the load.

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 names a concrete resource — market sessions across stock exchanges, forex, futures and crypto — including DST/holiday/early-close handling, so an agent knows exactly what it returns. It does not, however, contrast itself with siblings like get_market_overlap or get_time, leaving the boundary to be inferred.

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?

Use is only implied: an agent can guess this is for checking whether a market session is open on a given date. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative such as get_market_overlap for intersection questions.

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

All ItsNineThere tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?