Skip to main content

FX Context

by com.coco-pier

Overview Discussions Admin

get_market_reaction

get_market_reaction

Read-onlyIdempotent

Retrieve deterministic post-event market reaction metrics for an economic release or monetary policy statement.

Specify the targetType, such as US_CPI, US_PCE (alias PCE), US_NONFARM_PAYROLLS (alias NFP), US_ISM_MANUFACTURING (alias ISM_MANUFACTURING), US_ISM_SERVICES (alias ISM_SERVICES), FEDERAL_RESERVE, ECB, BANK_OF_ENGLAND (alias BOE), or BANK_OF_JAPAN (alias BOJ).

Optionally specify dateOrPeriod:

For US_CPI, US_PCE, US_NONFARM_PAYROLLS, and the ISM PMIs: reference period in YYYY-MM format (e.g. 2024-07). If omitted, the latest event is resolved.
For FEDERAL_RESERVE, ECB, BANK_OF_ENGLAND, or BANK_OF_JAPAN: statement date in YYYY-MM-DD format (e.g. 2024-08-01). If omitted, the latest statement is resolved.

Optionally specify instrument: EURUSD, GBPUSD, or USDJPY (defaults to EURUSD).

Returns deterministic price action metrics across 5 standardized post-event windows (M5, M15, H1, H4, H24) including startPrice, endPrice, returnPct, high, low, maxUpMovePct, maxDownMovePct, and rangePct.

All calculations are strictly deterministic and mathematical. This tool does not provide trading recommendations or predictive signals.

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": {
      "targetType": "<targetType>"
    },
    "name": "get_market_reaction"
  }
}

Input Schema

Name	Required	Description	Default
`instrument`	No	Optional trading instrument: EURUSD, GBPUSD, or USDJPY. Defaults to EURUSD.
`targetType`	Yes	Canonical target event type: US_CPI, US_PCE (alias PCE), US_NONFARM_PAYROLLS (alias NFP), US_ISM_MANUFACTURING (alias ISM_MANUFACTURING), US_ISM_SERVICES (alias ISM_SERVICES), FEDERAL_RESERVE, ECB, BANK_OF_ENGLAND (alias BOE), or BANK_OF_JAPAN (alias BOJ).
`dateOrPeriod`	No	Optional reference period (YYYY-MM for US_CPI, US_PCE, US_NONFARM_PAYROLLS, and the ISM PMIs) or statement date (YYYY-MM-DD for central banks). If omitted, the latest event is returned.

Output Schema

Name	Required	Description	Default
`windows`	Yes
`targetId`	Yes
`eventTime`	Yes
`freshness`	No
`isSettled`	Yes
`instrument`	Yes
`isComplete`	Yes
`reactionId`	Yes
`targetType`	Yes
`calculatedAt`	Yes
`coverageStatus`	No
`marketDataSource`	Yes
`reactionCoverage`	No
`targetDescription`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 10, 2026

changedInput schema / properties / targetType / description

Previous value: -"Canonical target event type: US_CPI, US_PCE (alias PCE), US_NONFARM_PAYROLLS (alias NFP), US_ISM_MANUFACTURING, US_ISM_SERVICES, FEDERAL_RESERVE, ECB, BANK_OF_ENGLAND (alias BOE), or BANK_OF_JAPAN (alias BOJ)."New value: +"Canonical target event type: US_CPI, US_PCE (alias PCE), US_NONFARM_PAYROLLS (alias NFP), US_ISM_MANUFACTURING (alias ISM_MANUFACTURING), US_ISM_SERVICES (alias ISM_SERVICES), FEDERAL_RESERVE, ECB, BANK_OF_ENGLAND (alias BOE), or BANK_OF_JAPAN (alias BOJ)."

Changed2 schema fields changedOct 10, 2026

changedInput schema / properties / dateOrPeriod / description

Previous value: -"Optional reference period (YYYY-MM for US_CPI, US_PCE, and US_NONFARM_PAYROLLS) or statement date (YYYY-MM-DD for central banks). If omitted, the latest event is returned."New value: +"Optional reference period (YYYY-MM for US_CPI, US_PCE, US_NONFARM_PAYROLLS, and the ISM PMIs) or statement date (YYYY-MM-DD for central banks). If omitted, the latest event is returned."

changedInput schema / properties / targetType / description

Previous value: -"Canonical target event type: US_CPI, US_PCE (alias PCE), US_NONFARM_PAYROLLS (alias NFP), FEDERAL_RESERVE, ECB, BANK_OF_ENGLAND (alias BOE), or BANK_OF_JAPAN (alias BOJ)."New value: +"Canonical target event type: US_CPI, US_PCE (alias PCE), US_NONFARM_PAYROLLS (alias NFP), US_ISM_MANUFACTURING, US_ISM_SERVICES, FEDERAL_RESERVE, ECB, BANK_OF_ENGLAND (alias BOE), or BANK_OF_JAPAN (alias BOJ)."

Changed2 schema fields changedSep 23, 2026

changedInput schema / properties / dateOrPeriod / description

Previous value: -"Optional reference period (YYYY-MM for US_CPI and US_NONFARM_PAYROLLS) or statement date (YYYY-MM-DD for central banks). If omitted, the latest event is returned."New value: +"Optional reference period (YYYY-MM for US_CPI, US_PCE, and US_NONFARM_PAYROLLS) or statement date (YYYY-MM-DD for central banks). If omitted, the latest event is returned."

changedInput schema / properties / targetType / description

Previous value: -"Canonical target event type: US_CPI, US_NONFARM_PAYROLLS (alias NFP), FEDERAL_RESERVE, ECB, BANK_OF_ENGLAND (alias BOE), or BANK_OF_JAPAN (alias BOJ)."New value: +"Canonical target event type: US_CPI, US_PCE (alias PCE), US_NONFARM_PAYROLLS (alias NFP), FEDERAL_RESERVE, ECB, BANK_OF_ENGLAND (alias BOE), or BANK_OF_JAPAN (alias BOJ)."

Changed2 schema fields changedSep 20, 2026

changedInput schema / properties / dateOrPeriod / description

Previous value: -"Optional reference period (YYYY-MM for US_CPI) or statement date (YYYY-MM-DD for central banks). If omitted, the latest event is returned."New value: +"Optional reference period (YYYY-MM for US_CPI and US_NONFARM_PAYROLLS) or statement date (YYYY-MM-DD for central banks). If omitted, the latest event is returned."

changedInput schema / properties / targetType / description

Previous value: -"Canonical target event type: US_CPI, FEDERAL_RESERVE, ECB, BANK_OF_ENGLAND (alias BOE), or BANK_OF_JAPAN (alias BOJ)."New value: +"Canonical target event type: US_CPI, US_NONFARM_PAYROLLS (alias NFP), FEDERAL_RESERVE, ECB, BANK_OF_ENGLAND (alias BOE), or BANK_OF_JAPAN (alias BOJ)."

Changed1 schema field changedSep 20, 2026

changedInput schema / properties / targetType / description

Previous value: -"Canonical target event type: US_CPI, FEDERAL_RESERVE, ECB, or BANK_OF_ENGLAND."New value: +"Canonical target event type: US_CPI, FEDERAL_RESERVE, ECB, BANK_OF_ENGLAND (alias BOE), or BANK_OF_JAPAN (alias BOJ)."

Changed1 schema field changedSep 20, 2026

changedInput schema / properties / targetType / description

Previous value: -"Canonical target event type: US_CPI, FEDERAL_RESERVE, or ECB."New value: +"Canonical target event type: US_CPI, FEDERAL_RESERVE, ECB, or BANK_OF_ENGLAND."

Changed1 schema field changedSep 19, 2026

changedInput schema / properties / instrument / description

Previous value: -"Optional trading instrument. Defaults to EURUSD."New value: +"Optional trading instrument: EURUSD, GBPUSD, or USDJPY. Defaults to EURUSD."

First observedSep 18, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: the calculations are strictly deterministic/mathematical and the tool emits no recommendations or predictive signals, which sets expectations about output trustworthiness.

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 first sentence and the closing determinism caveat are well front-loaded, but the middle two bullets reproduce the input schema's parameter descriptions nearly verbatim, so a substantial portion of the text duplicates structured data rather than earning 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?

Given an output schema exists, the description need not explain return fields, yet it still covers all required call inputs (event type, date/period format per event family, instrument) and whether omission is allowed. It is complete enough to call correctly, with only the sibling boundary left implicit.

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 three parameters including valid targetType values, date formats, and the default instrument. The description largely restates this (including the alias lists and YYYY-MM/YYYY-MM-DD formats) rather than adding new semantics, so the 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 ('Retrieve deterministic post-event market reaction metrics') and scopes it to economic releases and monetary policy statements. It is clear on its own, but it never positions itself against close siblings like get_historical_reaction_context or get_event_context, so the agent must infer the boundary.

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?

Usage context is clear: pick a targetType, optionally a dateOrPeriod, and an instrument, with omitted fields defaulting to latest/EURUSD. However, there is no explicit when-not-to-use guidance or naming of alternative siblings, which is notable given six siblings exist.

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

All FX Context tools Inspect

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?