FXMacroData

FX Market Sessions

market_sessions

Read-only

Returns which FX trading sessions are currently open (Sydney, Tokyo, London, New York) and when the next session opens or closes, for questions such as 'is the market open?', 'when does London open?', or 'which sessions overlap right now?'. An ISO-8601 UTC timestamp in at returns the snapshot for a specific moment instead of now. Accounts for weekends and major banking holidays. Access: free, no API key required.

Input Schema

Name	Required	Description	Default
`at`	No	Optional ISO-8601 UTC timestamp; defaults to now. Use to snapshot session state at a specific moment.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 5, 2026
- removedInput schema / properties / at / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / at / default
```
Removed value: -null
```
- addedInput schema / properties / at / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedInput schema / title
```
Removed value: -"market_sessionsArguments"
```
Changed1 schema field changedSep 7, 2026
- removedInput schema / properties / at / title
```
Removed value: -"At"
```

Changed2 schema fields changedMay 21, 2026

addedInput schema / properties / at / description

Added value: +"Optional ISO-8601 UTC timestamp; defaults to now. Use to snapshot session state at a specific moment."

addedInput schema / properties / at / examples

Added value: +[
+  "2025-06-15T13:30:00Z",
+  "2025-12-25T00:00:00Z"
+]

First observedApr 15, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: weekend and major banking holiday handling, plus free/no-API-key access. It stops short of describing output shape or edge cases such as holidays with partial session closures.

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-loaded with the return payload, then the example use cases, then the optional parameter override, then access terms. Three sentences with no filler; every clause carries decision-relevant information.

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 an output schema present, the description needn't explain return values, and one optional parameter is fully covered. Holiday/weekend handling and free access are disclosed, leaving only minor gaps like how partial holidays are treated.

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%, and the schema already specifies the ISO-8601 UTC format, examples, nullability, and the 'defaults to now' behavior. The description's 'instead of now' framing restates the schema rather than adding new meaning, so the baseline 3 applies.

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?

Names the specific resource (FX trading sessions) and the exact payload (which sessions are open plus the next open/close), and enumerates the four sessions. It is clearly distinguishable from siblings like forex or risk_sentiment, which concern prices and sentiment rather than session state.

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?

The quoted example questions ('is the market open?', 'when does London open?', 'which sessions overlap right now?') give strong when-to-use context, and the `at` sentence explains the historical-snapshot case. It does not name an alternative sibling or state when not to use it, so it falls short of a 5.

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

All FXMacroData 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.