Skip to main content
Glama

market-open

US market session state. No input: the NYSE regular session (9:30 to 4:00 ET) with the closed / pre-market / regular / after-hours ladder, the next open or close with its exact countdown, the next holiday with its day count, the DST-aware New York clock, and the 2026 and 2027 closure and early-close calendars, answered fresh on every call. Price: $0.10 per call, paid in USDC on Base mainnet over x402; an unpaid call answers HTTP 402 with the exact machine-readable payment terms.

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": "market-open"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations the description carries the full burden and does so well: it discloses freshness ("answered fresh on every call"), cost ($0.10 per call), payment rail (USDC on Base mainnet over x402), and failure behavior (unpaid call returns HTTP 402 with machine-readable terms). That is meaningful operational context an agent cannot get from the empty schema. It stops short of describing response shape or latency/timeout behavior.

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?

The name and the identity of the resource are front-loaded, and every clause enumerates concrete return content rather than filler. It is dense and runs long as a single block, and the payment sentence could be split out, but no sentence is wasted.

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 no annotations, no output schema, and no parameters, the description is the only documentation, and it covers content coverage, date range, freshness, and pricing/payment flow. What is missing is any indication of the response format or a sample field set, which an agent would need to consume the output confidently.

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?

There are zero parameters, so the baseline is 4 per the rubric. The description's "No input" clause usefully confirms the empty schema rather than leaving it ambiguous whether inputs were omitted.

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 gives a specific resource ("US market session state") and enumerates exactly what it returns: the closed/pre-market/regular/after-hours ladder, next open/close countdown, next holiday, DST-aware NY clock, and 2026-2027 closure calendars. That is far beyond a tautology. It loses the top band because it never differentiates itself from overlapping siblings such as next-federal-holiday or dst-state, leaving the agent to infer which tool owns the holiday/DST answer.

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?

"No input" tells the agent how to invoke it and the content list implies the questions it answers, but there is no explicit when-to-use or when-not statement and no named alternative. For a zero-parameter snapshot tool this is largely self-evident, so the gap is mild rather than disqualifying.

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