Skip to main content
Glama

TradeTi.me — Market Hours

by io.github.NicolaiJohannesen
OverviewAdmin

time_until_next_open

Read-onlyIdempotent

When does an exchange next open? Returns hours until the next open (weekends and holidays skipped), or — if it is already open — hours until it closes.

Input Schema

TableJSON 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. Dates show when Glama detected each change.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already indicate readOnly and idempotent; description additionally discloses that weekends and holidays are skipped, and the dual open/close behavior. Adds useful context beyond annotations.

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 concise sentences, front-loaded with the core question. Every word adds value; no filler.

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?

Given no output schema, the description covers the primary functionality and key exclusions (weekends/holidays). Could specify return format, but overall adequate for a simple tool.

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 coverage is 100% with detailed parameter descriptions. The description reinforces the overall calculation but adds minimal parameter-specific meaning beyond what's in the schema.

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 description clearly states the tool returns hours until next open or close, with specifics on weekends and holidays. It differentiates from siblings like is_market_open and markets_open_now by focusing on future timing.

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?

No explicit guidance on when to use this tool versus alternatives. The schema hints at use cases via the at parameter, but the description itself does not differentiate from siblings.

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

All TradeTi.me — Market Hours toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources