FXMacroData

FX Trade Setup Analysis

fx_trade_setup_task

Read-only

Build a trader-oriented FX pair setup using spot context, macro differentials, upcoming catalyst risk, and optional COT positioning. Set view for pair context only or a ranked event-risk score. 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": {
      "base": "<base>",
      "quote": "<quote>"
    },
    "name": "fx_trade_setup_task"
  }
}

Input Schema

Name	Required	Description	Default
`base`	Yes	Base currency, 3-letter ISO code. Supported: lowercase 3-letter catalogue currency, e.g. usd or eur.
`view`	No	setup (default) builds the full trade setup. pair_intel returns spot, carry and policy-differential context. release_risk ranks upcoming event risk for the pair.	setup
`quote`	Yes	Quote currency, 3-letter ISO code. Supported: lowercase 3-letter catalogue currency, e.g. usd or eur.
`end_date`	No	view='pair_intel' only: inclusive upper bound, YYYY-MM-DD.
`start_date`	No	view='pair_intel' only: inclusive lower bound, YYYY-MM-DD.
`include_cot`	No	When true, attempt to include COT positioning context for both legs.
`horizon_events`	No	Maximum upcoming catalysts per leg to rank. Defaults to 4, or 6 for view='release_risk'.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 7, 2026

addedInput schema / properties / end_date

Added value: +{
+  "description": "view='pair_intel' only: inclusive upper bound, YYYY-MM-DD.",
+  "examples": [
+    "2024-06-30"
+  ],
+  "type": [
+    "string",
+    "null"
+  ]
+}

removedInput schema / properties / horizon_events / default
```
Removed value: -4
```

changedInput schema / properties / horizon_events / description

Previous value: -"Maximum upcoming catalysts per leg to rank."New value: +"Maximum upcoming catalysts per leg to rank. Defaults to 4, or 6 for view='release_risk'."

addedInput schema / properties / start_date

Added value: +{
+  "description": "view='pair_intel' only: inclusive lower bound, YYYY-MM-DD.",
+  "examples": [
+    "2024-06-30"
+  ],
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedInput schema / properties / view

Added value: +{
+  "default": "setup",
+  "description": "setup (default) builds the full trade setup. pair_intel returns spot, carry and policy-differential context. release_risk ranks upcoming event risk for the pair.",
+  "enum": [
+    "setup",
+    "pair_intel",
+    "release_risk"
+  ],
+  "type": "string"
+}

Changed7 schema fields changedNov 5, 2026

changedInput schema / properties / base / description

Previous value: -"Base currency, 3-letter ISO code. Supported: any lowercase 3-letter ISO code in the FXMacroData catalogue, for example usd, eur, gbp, jpy."New value: +"Base currency, 3-letter ISO code. Supported: lowercase 3-letter catalogue currency, e.g. usd or eur."

removedInput schema / properties / horizon_events / anyOf

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

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

removedInput schema / properties / include_cot / anyOf

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

addedInput schema / properties / include_cot / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```

changedInput schema / properties / quote / description

Previous value: -"Quote currency, 3-letter ISO code. Supported: any lowercase 3-letter ISO code in the FXMacroData catalogue, for example usd, eur, gbp, jpy."New value: +"Quote currency, 3-letter ISO code. Supported: lowercase 3-letter catalogue currency, e.g. usd or eur."

removedInput schema / title

Removed value: -"fx_trade_setup_taskArguments"

Changed2 schema fields changedOct 31, 2026

changedInput schema / properties / base / description

Previous value: -"Base currency, 3-letter ISO code. Supported: AUD, BRL, CAD, CHF, CNH, CNY, DKK, EUR, GBP, HUF, ILS, JPY, KRW, MYR, NGN, NOK, NZD, PEN, SEK, THB, TWD, USD."New value: +"Base currency, 3-letter ISO code. Supported: any lowercase 3-letter ISO code in the FXMacroData catalogue, for example usd, eur, gbp, jpy."

changedInput schema / properties / quote / description

Previous value: -"Quote currency, 3-letter ISO code. Supported: AUD, BRL, CAD, CHF, CNH, CNY, DKK, EUR, GBP, HUF, ILS, JPY, KRW, MYR, NGN, NOK, NZD, PEN, SEK, THB, TWD, USD."New value: +"Quote currency, 3-letter ISO code. Supported: any lowercase 3-letter ISO code in the FXMacroData catalogue, for example usd, eur, gbp, jpy."

Changed2 schema fields changedSep 11, 2026

changedInput schema / properties / base / description

Previous value: -"Base currency, 3-letter ISO code. Supported: AUD, BRL, CAD, CHF, CNH, CNY, DKK, EUR, GBP, ILS, JPY, NGN, NOK, NZD, PEN, SEK, THB, USD."New value: +"Base currency, 3-letter ISO code. Supported: AUD, BRL, CAD, CHF, CNH, CNY, DKK, EUR, GBP, HUF, ILS, JPY, KRW, MYR, NGN, NOK, NZD, PEN, SEK, THB, TWD, USD."

changedInput schema / properties / quote / description

Previous value: -"Quote currency, 3-letter ISO code. Supported: AUD, BRL, CAD, CHF, CNH, CNY, DKK, EUR, GBP, ILS, JPY, NGN, NOK, NZD, PEN, SEK, THB, USD."New value: +"Quote currency, 3-letter ISO code. Supported: AUD, BRL, CAD, CHF, CNH, CNY, DKK, EUR, GBP, HUF, ILS, JPY, KRW, MYR, NGN, NOK, NZD, PEN, SEK, THB, TWD, USD."

Changed4 schema fields changedSep 7, 2026
- removedInput schema / properties / base / title
```
Removed value: -"Base"
```
- removedInput schema / properties / horizon_events / title
```
Removed value: -"Horizon Events"
```
- removedInput schema / properties / include_cot / title
```
Removed value: -"Include Cot"
```
- removedInput schema / properties / quote / title
```
Removed value: -"Quote"
```

Changed2 schema fields changedJul 8, 2026

changedInput schema / properties / base / description

Previous value: -"Base currency, 3-letter ISO code. Supported: AUD, BRL, CAD, CHF, CNH, CNY, DKK, EUR, GBP, IDR, ILS, JPY, NGN, NOK, NZD, PEN, SEK, THB, USD."New value: +"Base currency, 3-letter ISO code. Supported: AUD, BRL, CAD, CHF, CNH, CNY, DKK, EUR, GBP, ILS, JPY, NGN, NOK, NZD, PEN, SEK, THB, USD."

changedInput schema / properties / quote / description

Previous value: -"Quote currency, 3-letter ISO code. Supported: AUD, BRL, CAD, CHF, CNH, CNY, DKK, EUR, GBP, IDR, ILS, JPY, NGN, NOK, NZD, PEN, SEK, THB, USD."New value: +"Quote currency, 3-letter ISO code. Supported: AUD, BRL, CAD, CHF, CNH, CNY, DKK, EUR, GBP, ILS, JPY, NGN, NOK, NZD, PEN, SEK, THB, USD."

Changed2 schema fields changedJul 4, 2026

changedInput schema / properties / base / description

Previous value: -"Base currency, 3-letter ISO code. Supported: AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, NGN, NOK, NZD, PEN, SEK, THB, USD."New value: +"Base currency, 3-letter ISO code. Supported: AUD, BRL, CAD, CHF, CNH, CNY, DKK, EUR, GBP, IDR, ILS, JPY, NGN, NOK, NZD, PEN, SEK, THB, USD."

changedInput schema / properties / quote / description

Previous value: -"Quote currency, 3-letter ISO code. Supported: AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, NGN, NOK, NZD, PEN, SEK, THB, USD."New value: +"Quote currency, 3-letter ISO code. Supported: AUD, BRL, CAD, CHF, CNH, CNY, DKK, EUR, GBP, IDR, ILS, JPY, NGN, NOK, NZD, PEN, SEK, THB, USD."

Changed2 schema fields changedJun 28, 2026

changedInput schema / properties / base / description

Previous value: -"Base currency, 3-letter ISO code. Supported: AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, NGN, NZD, PEN, SEK, THB, USD."New value: +"Base currency, 3-letter ISO code. Supported: AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, NGN, NOK, NZD, PEN, SEK, THB, USD."

changedInput schema / properties / quote / description

Previous value: -"Quote currency, 3-letter ISO code. Supported: AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, NGN, NZD, PEN, SEK, THB, USD."New value: +"Quote currency, 3-letter ISO code. Supported: AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, NGN, NOK, NZD, PEN, SEK, THB, USD."

Changed2 schema fields changedJun 28, 2026

changedInput schema / properties / base / description

Previous value: -"Base currency, 3-letter ISO code. Supported: AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, NZD, PEN, SEK, THB, USD."New value: +"Base currency, 3-letter ISO code. Supported: AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, NGN, NZD, PEN, SEK, THB, USD."

changedInput schema / properties / quote / description

Previous value: -"Quote currency, 3-letter ISO code. Supported: AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, NZD, PEN, SEK, THB, USD."New value: +"Quote currency, 3-letter ISO code. Supported: AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, NGN, NZD, PEN, SEK, THB, USD."

Changed2 schema fields changedJun 27, 2026

changedInput schema / properties / base / description

Previous value: -"Base currency, 3-letter ISO code. Supported: AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, NZD, PEN, SEK, USD."New value: +"Base currency, 3-letter ISO code. Supported: AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, NZD, PEN, SEK, THB, USD."

changedInput schema / properties / quote / description

Previous value: -"Quote currency, 3-letter ISO code. Supported: AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, NZD, PEN, SEK, USD."New value: +"Quote currency, 3-letter ISO code. Supported: AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, NZD, PEN, SEK, THB, USD."

Changed2 schema fields changedJun 25, 2026

changedInput schema / properties / base / description

Previous value: -"Base currency, 3-letter ISO code. Supported: AED, AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, MXN, NZD, PEN, PLN, SEK, THB, TWD, USD."New value: +"Base currency, 3-letter ISO code. Supported: AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, NZD, PEN, SEK, USD."

changedInput schema / properties / quote / description

Previous value: -"Quote currency, 3-letter ISO code. Supported: AED, AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, MXN, NZD, PEN, PLN, SEK, THB, TWD, USD."New value: +"Quote currency, 3-letter ISO code. Supported: AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, NZD, PEN, SEK, USD."

Changed2 schema fields changedJun 25, 2026

changedInput schema / properties / base / description

Previous value: -"Base currency, 3-letter ISO code. Supported: AED, AUD, BRL, CAD, CHF, DKK, EUR, GBP, IDR, ILS, JPY, MXN, NZD, PEN, PLN, SEK, THB, TWD, USD."New value: +"Base currency, 3-letter ISO code. Supported: AED, AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, MXN, NZD, PEN, PLN, SEK, THB, TWD, USD."

changedInput schema / properties / quote / description

Previous value: -"Quote currency, 3-letter ISO code. Supported: AED, AUD, BRL, CAD, CHF, DKK, EUR, GBP, IDR, ILS, JPY, MXN, NZD, PEN, PLN, SEK, THB, TWD, USD."New value: +"Quote currency, 3-letter ISO code. Supported: AED, AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, MXN, NZD, PEN, PLN, SEK, THB, TWD, USD."

AddedJun 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds genuinely new behavioral context beyond structured fields: API key gating and the exact failure mode (subscription_required with a subscribe link), plus the fact that COT inclusion is best-effort ("attempt to include"). It stops short of describing the shape or size of the returned setup.

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?

Three short sentences with the core purpose front-loaded and no filler. The middle sentence ("Set view for pair context only or a ranked event-risk score") is compressed to the point of being slightly ambiguous, which keeps it from a 5.

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 7-parameter, three-mode composite task with no output schema, the description covers purpose, input dimensions, mode semantics, and access gating. What is missing is any sense of return shape or output size, which matters more here precisely because no output schema exists to carry that burden.

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%, so every parameter including the view enum and date bounds is already fully documented in the schema. The description only echoes the optional COT positioning and catalyst risk at a high level, adding no syntax, format, or interaction detail beyond what structured data provides. 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?

The description states a specific verb and resource ("Build a trader-oriented FX pair setup") and enumerates the input dimensions it fuses: spot context, macro differentials, catalyst risk, and optional COT positioning. It does not name any sibling tool (forex, cot_data, rate_differentials, release_calendar) it overlaps with, so differentiation is left implicit.

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?

It gives some mode-selection guidance ("view for pair context only or a ranked event-risk score"), but this largely restates the view enum already documented in the schema. There is no guidance on when to use this composite task versus calling the primitive siblings (forex, cot_data, release_calendar) directly, nor on when the extra latency of a full setup is justified.

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.

FX Trade Setup Analysis

Tool call template

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources