Skip to main content
Glama

headless-oracle

by io.github.LembaGang
OverviewDiscussionsAdmin

get_market_schedule

Returns holiday-aware trading session schedule with next open/close UTC timestamps for any of 28 exchanges. Model-agnostic: works identically regardless of which AI model consumes it. Pairs with get_market_status signed receipts. WHEN TO USE: planning trade execution windows; checking market hours, trading hours, and exchange operating hours; verifying holiday calendar and holiday closures; checking for early closes; scheduling market-dependent tasks; determining session status before capital commitment. Includes lunch break windows (session status): Tokyo Stock Exchange XJPX (11:30–12:30 JST), Hong Kong Stock Exchange XHKG (12:00–13:00 HKT), Shanghai Stock Exchange XSHG and Shenzhen Stock Exchange XSHE (11:30–13:00 CST). Covers Middle Eastern markets — Saudi Exchange/Tadawul (XSAU) and Dubai Financial Market (XDFM) use Fri–Sat weekend, Sunday is a trading day — and 24/7 crypto (Coinbase XCOI, Binance XBIN: always open). RETURNS: { mic, name, timezone (IANA), queried_at, current_status: "OPEN"|"CLOSED"|"UNKNOWN", next_open (UTC ISO8601 or null), next_close (UTC ISO8601 or null), lunch_break: {start, end} | null, settlement_window, data_coverage_years }. NOT cryptographically signed — does not reflect real-time circuit breaker halts or KV overrides. For authoritative signed status use get_market_status. Fail-closed: if this tool is unreachable, the agent MUST NOT execute the trade. LATENCY: sub-100ms p95 (pure schedule computation, no signing).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
micNoISO 10383 Market Identifier Code. Defaults to XNYS (NYSE). Call list_exchanges to see all 28 supported codes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed2 schema fields changed
    • changedInput schema / properties / mic / description
      Previous value: -"ISO 10383 Market Identifier Code. Defaults to XNYS (NYSE). Call list_exchanges to see all 23 supported codes."New value: +"ISO 10383 Market Identifier Code. Defaults to XNYS (NYSE). Call list_exchanges to see all 28 supported codes."
    • changedInput schema / properties / mic / enum
      Previous value: -[
-  "XNYS",
-  "XNAS",
-  "XLON",
-  "XJPX",
-  "XPAR",
-  "XHKG",
-  "XSES",
-  "XASX",
-  "XBOM",
-  "XNSE",
-  "XSHG",
-  "XSHE",
-  "XKRX",
-  "XJSE",
-  "XBSP",
-  "XSWX",
-  "XMIL",
-  "XIST",
-  "XSAU",
-  "XDFM",
-  "XNZE",
-  "XHEL",
-  "XSTO"
-]New value: +[
+  "XNYS",
+  "XNAS",
+  "XLON",
+  "XJPX",
+  "XPAR",
+  "XHKG",
+  "XSES",
+  "XASX",
+  "XBOM",
+  "XNSE",
+  "XSHG",
+  "XSHE",
+  "XKRX",
+  "XJSE",
+  "XBSP",
+  "XSWX",
+  "XMIL",
+  "XIST",
+  "XSAU",
+  "XDFM",
+  "XNZE",
+  "XHEL",
+  "XSTO",
+  "XCBT",
+  "XNYM",
+  "XCBO",
+  "XCOI",
+  "XBIN"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / mic / description
      Previous value: -"Exchange identifier (MIC code). Common values: XNYS=NYSE, XNAS=NASDAQ, XLON=London, XJPX=Tokyo, XPAR=Paris, XHKG=Hong Kong, XSES=Singapore. Defaults to XNYS."New value: +"ISO 10383 Market Identifier Code. Defaults to XNYS (NYSE). Call list_exchanges to see all 23 supported codes."
  4. Changed1 schema field changed
    • changedInput schema / properties / mic / enum
      Previous value: -[
-  "XNYS",
-  "XNAS",
-  "XLON",
-  "XJPX",
-  "XPAR",
-  "XHKG",
-  "XSES"
-]New value: +[
+  "XNYS",
+  "XNAS",
+  "XLON",
+  "XJPX",
+  "XPAR",
+  "XHKG",
+  "XSES",
+  "XASX",
+  "XBOM",
+  "XNSE",
+  "XSHG",
+  "XSHE",
+  "XKRX",
+  "XJSE",
+  "XBSP",
+  "XSWX",
+  "XMIL",
+  "XIST",
+  "XSAU",
+  "XDFM",
+  "XNZE",
+  "XHEL",
+  "XSTO"
+]
  5. First observed

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It goes beyond the basic return type to disclose that results are not cryptographically signed, do not reflect real-time circuit breaker halts or KV overrides, are fail-closed if unreachable, and have sub-100ms p95 latency. It also documents session nuances like lunch breaks and Middle East weekends.

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?

The description is long but every section earns its place: purpose, usage triggers, return shape, caveats, and latency. It is front-loaded with the core definition absent any filler, and the labeled sections and bolded callouts make the key operational constraints scannable for an agent.

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?

Given that this tool has a single optional parameter literated in the schema, no output schema, and no annotations, the description compensates fully by enumerating every return field, documenting edge cases, naming sibling alternatives, and stating a fail-closed safety requirement. An agent has everything needed to decide when to call it and what to expect.

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%: the schema fully documents the single 'mic' parameter as an ISO 10383 Market Identifier Code with an enum of 28 values, a default of XNYS, and a pointer to list_exchanges. The description adds contextual examples of specific exchanges and their behaviors, but the core parameter semantics are already fully covered by the schema, so a baseline 3 is appropriate.

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 opens with a specific verb and resource: 'Returns holiday-aware trading session schedule with next open/close UTC timestamps for any of 28 exchanges.' It clearly distinguishes itself from siblings by focusing on schedule computation rather than status verification, and it explicitly names get_market_status as the authoritative alternative.

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?

An explicit 'WHEN TO USE' section lists concrete use cases such as planning trade execution windows and checking holiday closures. It also provides an exclusion: 'NOT cryptographically signed... For authoritative signed status use get_market_status,' and adds a fail-closed directive. This is exceptionally clear routing guidance.

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

All headless-oracle toolsInspect
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