Skip to main content
Glama

TradeTi.me — Market Hours

get_trading_sessions

Read-onlyIdempotent

The trading-session structure for one exchange, in exchange-local decimal hours (9.5 = 09:30). A four-number "main" means a lunch break (e.g. Tokyo 9–11.5, 12.5–15.5).

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

Input Schema

NameRequiredDescriptionDefault
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.6/5.0
Behavior4/5

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

Annotations already declare this as a safe, idempotent, closed-world read, so the safety profile is covered. The description earns credit for disclosing the return encoding (decimal hours where 9.5 = 09:30) and the semantic meaning of a four-number main entry (a lunch break, with a Tokyo example) — output-shape information that annotations cannot carry and that no output schema supplies.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, with the core resource and its unit convention front-loaded before the interpretive example. Every clause carries information an agent could not get elsewhere; nothing is redundant with the schema or annotations.

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 one-parameter read tool with no output schema, the description supplies the essential output encoding and the lunch-break convention, which is the main ambiguity risk. It stops short of describing the overall return shape (e.g. whether pre/post-market or weekday variants appear), leaving a modest gap given there is no output schema to fall back on.

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 single `exchange` parameter already documents id-or-name matching, case-insensitivity, and examples. The description adds nothing about the parameter beyond the schema, so the baseline 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 names the specific resource (trading-session structure) and its scope (one exchange, exchange-local decimal hours), which is concrete enough to distinguish it from siblings like get_exchange_status or is_market_open. It does not, however, explicitly contrast itself with those siblings, so an agent must infer the boundary.

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 when-to-use guidance, no mention of when to prefer this over get_exchange_status, is_market_open, or markets_open_now, and no stated exclusions. Usage is only inferable from the resource name, which is exactly the gap this dimension measures.

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