Skip to main content
Glama

FinanceQuery

Market Hours

get_market_hours
Read-onlyIdempotent

Get current market hours and open/closed status for a region.

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": {
      "region": "<region>"
    },
    "name": "get_market_hours"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated list of GraphQL field names to include; omitted = all fields
regionYesRegion code: US|GB|DE|CA|AU|FR|IN|CN|HK|BR|TW|SG (default: US)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety and side-effect profile is fully covered structurally. The description adds only the 'current' temporal framing and the fact that an open/closed boolean-like status is returned; it says nothing about timezone handling, holiday behavior, or staleness of the response.

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?

A single front-loaded sentence with no filler or redundancy; the resource appears before the qualifier. It is efficient, though the terseness is arguably a symptom of missing guidance rather than editorial discipline.

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 simple two-parameter read-only lookup with a fully described schema and rich annotations, this is close to sufficient. The main remaining gap is what 'current' means operationally (exchange-local time vs. UTC, behavior outside trading days), which matters for an openWorldHint tool returning live status.

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%: the region parameter already enumerates all supported region codes and its default, and the fields parameter explains the comma-separated GraphQL field list. The description's mention of 'a region' merely echoes the schema, adding no format or behavioral detail, 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?

States a concrete verb ('Get') and two concrete resources ('current market hours' and 'open/closed status') scoped by region, so it is readily distinguishable from get_market_calendar (calendar/schedule data) and get_market_summary. It stops short of explicitly naming those siblings, but the resource itself is specific.

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?

The word 'current' implies this is for real-time status rather than historical or scheduled data, which is useful, but there is no explicit when-to-use statement, no exclusions, and no reference to an alternative such as get_market_calendar for future sessions.

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.