FXMacroData

FX Seasonality

seasonality

Read-only

Get monthly return seasonality for an FX pair or XAU/USD, covering seasonal patterns, month-of-year tendency, historical monthly win rate, and XAUUSD/gold seasonality. Returns monthly average return, median return, win rate, sample size, dispersion, and per-year monthly returns from stored FX or gold series. Access: API key required, else returns subscription_required with a subscribe link.

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": {
      "instrument": "<instrument>"
    },
    "name": "seasonality"
  }
}

Input Schema

Name	Required	Description
`month`	No	Optional month filter, 1-12 or name such as July.
`end_date`	No	Inclusive upper bound, YYYY-MM-DD. Defaults to today.
`instrument`	Yes	Six-letter pair such as EURUSD, AUDUSD, USDJPY, or XAUUSD. Slashes and separators are accepted by the REST endpoint only when passed as a single string.
`lookback_years`	No	Number of years to include, 2-30. Defaults to 10.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedNov 5, 2026

removedInput schema / properties / end_date / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / end_date / default
```
Removed value: -null
```

changedInput schema / properties / end_date / examples

Previous value: -[
-  "2020-01-01",
-  "2024-06-30"
-]New value: +[
+  "2024-06-30"
+]

addedInput schema / properties / end_date / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedInput schema / properties / lookback_years / anyOf

Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / lookback_years / type
```
Added value: +[
+  "integer",
+  "null"
+]
```

removedInput schema / properties / month / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / month / default
```
Removed value: -null
```
addedInput schema / properties / month / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedInput schema / title
```
Removed value: -"seasonalityArguments"
```

Changed4 schema fields changedSep 7, 2026
- removedInput schema / properties / end_date / title
```
Removed value: -"End Date"
```
- removedInput schema / properties / instrument / title
```
Removed value: -"Instrument"
```
- removedInput schema / properties / lookback_years / title
```
Removed value: -"Lookback Years"
```
- removedInput schema / properties / month / title
```
Removed value: -"Month"
```
AddedJul 6, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context beyond them: an API key is required and failure returns a subscription_required payload with a subscribe link, which tells the agent how to handle a rejection. It also discloses the result shape (average, median, win rate, sample size, dispersion, per-year returns), though it does not describe pagination or data-refresh behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded in the first clause, which is good. However the opening sentence is padded with near-duplicate phrasing ('seasonal patterns, month-of-year tendency, historical monthly win rate, and XAUUSD/gold seasonality') that repeats XAU/USD and reads as keyword stuffing rather than information. The final access sentence earns its place.

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?

An output schema exists, so the description need not enumerate return fields, yet it does so briefly and consistently. Auth requirements and the subscription fallback are disclosed, and the instrument universe (six-letter pairs plus XAUUSD) is clear. What is missing is only the routing guidance relative to the large sibling set.

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%, so the schema already documents all four parameters including month formats, date bounds, and the 2-30 lookback range. The description adds only that the data comes from 'stored FX or gold series', which does not clarify any parameter behavior. Baseline 3 applies when the schema carries the parameter semantics.

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 specific verb and resource: 'Get monthly return seasonality for an FX pair or XAU/USD'. The scope is unambiguous and the term 'seasonality' separates it from generic siblings like forex or commodities. It stops short of explicitly naming a sibling it should be preferred over, so it is clear but not maximally differentiated.

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?

Usage is only implied: an agent can infer this is the tool for month-of-year return patterns on a currency or gold pair. There is no explicit when-to-use vs when-not, and no pointer to the sibling tools (forex, commodities) that would be used for non-seasonal price data. The access note does route the agent to subscribe_for_mcp_access indirectly via the subscription_required response.

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.