Skip to main content
Glama

WritersLogic business agents

market-session

Is the exchange in its core session at this instant? (NYSE holidays and 13:00 early closes, or a caller calendar) — For up to 50 caller-supplied instants, reports whether the NYSE core session (09:30-16:00 America/New_York, 13:00 on early-close days) is open, the reason when closed (weekend, named holiday, before open, after close), that day's open and close instants and the next open; or the same for a caller venue (zone, open, close, holidays, early closes). NYSE data is a dated snapshot of nyse.com covering

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": {
      "venue": "<venue>",
      "instants": "<instants>"
    },
    "name": "market-session"
  }
}

Input Schema

NameRequiredDescriptionDefault
openNovenue caller only, local HH:MM.
closeNovenue caller only, local HH:MM, after open.
venueYes
expectNoIf given, status is fail for any instant whose state differs.
weekendNoNon-business weekdays, 0=Sunday..6=Saturday. Default [0, 6]; use [5, 6] for a Friday/Saturday weekend.
holidaysNoExtra non-business dates YYYY-MM-DD (company closures, a calendar we do not carry).
instantsYesRFC 3339 timestamps with Z or offset.
timeZoneNovenue caller only.
earlyClosesNovenue caller only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does useful work: it enumerates the returned fields (status, closed reason, that day's open/close, next open) and discloses that the NYSE calendar is a dated snapshot of nyse.com, which signals data staleness. However, the final sentence is truncated mid-clause ('covering '), so the snapshot's actual coverage window is lost, and nothing is said about failure behavior for malformed instants or how `expect` mismatches surface beyond the schema note.

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

Conciseness3/5

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

The core question is front-loaded, which is correct, but the remainder is a single sprawling multi-clause sentence with a parenthetical, an em dash, and a semicolon chain. Worse, it terminates mid-sentence at 'nyse.com covering ', leaving visibly incomplete text that costs credibility and comprehension.

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?

This is a 9-parameter tool with no output schema, and the description compensates well by describing the return payload field by field, which is the most important gap to fill. It is only slightly short of complete: the truncated closing sentence leaves the NYSE snapshot's coverage period unknown, which matters for callers asking about dates outside that window.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 89%, so the baseline is 3; the description earns an increment by explaining why the caller-only parameters exist (venue zone, open, close, holidays, early closes) rather than merely naming them. It also frames the instants parameter as a bounded batch of up to 50 RFC 3339 timestamps, reinforcing the schema's maxItems.

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 opening question ('Is the exchange in its core session at this instant?') gives a specific predicate plus resource, and the body spells out both modes: NYSE core session with its exact window, or a caller-defined venue. An agent can tell immediately this is a point-in-time market-hours check, not a calendar conversion or predictor.

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

Usage Guidelines4/5

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

Usage context is clear: batch evaluation of up to 50 caller-supplied instants, with an explicit fork between NYSE mode and caller-venue mode (zone, open, close, holidays, early closes). It does not name an alternative tool or state when not to use this one, so it stops short of a routing rule.

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