Flexreport Finance

is_market_open

Read-only

Check whether an exchange is currently open — a cheap routing helper.

An unknown or wrong-case code returns a 400 "Exchange not found." error.

Returns `exchanges`, a one-element list; the answer is its `isMarketOpen` boolean.
The record also carries the session hours (`openingHour`/`closingHour` with UTC
offsets), `timezone`, and any additional-session bounds.

Use it to route between the market-hours tools: when the market is CLOSED,
extended-hours data lives in `get_aftermarket_data`;
when OPEN, `detect_intraday_outlier_jumps` gives the live intraday read.
No auth required.

Unsure which exchange a ticker trades on? `get_company_snapshot` returns an
`exchange` field whose value can be passed here as-is.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`exchange`	No	CASE-SENSITIVE uppercase exchange code, e.g. "NYSE", "NASDAQ", "LSE" (not full names). NYSE is right for US equities.	NYSE

Output Schema

TableJSON Schema

Name	Required	Description	Default
`exchanges`	Yes	One record for the requested exchange; read its isMarketOpen.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations only declare readOnlyHint=true; the description adds real behavioral context: unknown/wrong-case codes yield a 400 'Exchange not found.', no auth is required, and it discloses the return shape (one-element list, isMarketOpen boolean, session hours, timezone).

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?

Front-loads the core purpose and the error contract, then the routing guidance, then the code-sourcing tip. Multi-line but every sentence carries distinct, actionable information with no filler.

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?

Covered despite an existing output schema: error behavior, auth, routing, and parameter pitfalls are all addressed. Nothing an agent needs to call this correctly or act on the result is missing.

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 100% (baseline 3), and the description goes further by stressing the case-sensitivity pitfall, that full names are invalid, and that NYSE is the right default for US equities, plus how to source the value from get_company_snapshot.

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?

States a specific verb+resource ('check whether an exchange is currently open') and distinguishes itself from market-hours siblings as a 'cheap routing helper'. An agent immediately knows this is a lightweight status probe rather than a data-fetch tool.

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?

Gives explicit routing rules: when CLOSED, use get_aftermarket_data; when OPEN, use detect_intraday_outlier_jumps. It also handles the prior-step question of how to get a valid exchange code via get_company_snapshot.

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

All Flexreport Finance tools Inspect

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

Need Help?