Skip to main content
Glama

FXMacroData

by io.github.fxmacrodata
OverviewDiscussionsAdmin

FX Market Sessions

market_sessions
Read-only

Tell the user which FX trading sessions are currently open (Sydney, Tokyo, London, New York) and when the next session opens/closes. Use this when the user asks 'is the market open?', 'when does London open?', or 'which sessions overlap right now?'. Pass an ISO-8601 UTC timestamp via at to get the snapshot for a specific moment instead of now. Accounts for weekends and major banking holidays.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
atNoOptional ISO-8601 UTC timestamp; defaults to now. Use to snapshot session state at a specific moment.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / at / title
      Removed value: -"At"
  2. Changed2 schema fields changed
    • 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"
+]
  3. First observed

TDQS

A5/5.0
Behavior5/5

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

The description transparently notes that it accounts for weekends and major banking holidays, and the annotations (readOnlyHint, destructiveHint) already clarify it is read-only and non-destructive. No behavior is hidden or contradictory.

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?

The description is concise (three sentences) and front-loaded with the primary purpose. Every sentence adds value: purpose, usage examples, and parameter behavior. No redundant content.

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?

The tool has a single optional parameter, and the output schema is provided. Together with the description, an agent knows exactly what the tool does, when to call it, and what it returns. No gaps exist for successful invocation.

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

Parameters5/5

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

The only parameter 'at' is fully described in the schema and the description reinforces it as optional, defaulting to now, with an example format. 100% schema description coverage and no ambiguity.

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 ('Tell') and resource ('FX trading sessions'), clearly distinguishing the tool's purpose. It explicitly mentions the sessions (Sydney, Tokyo, London, New York) and the scope of the response (currently open, next opens/closes).

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?

Provides explicit example prompts ('is the market open?', 'when does London open?', 'which sessions overlap right now?') and explains when to pass the optional 'at' parameter for a specific moment. This fully guides an agent on when to invoke the tool.

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

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