FX Context

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), FEDERAL_RESERVE, ECB, BANK_OF_ENGLAND (alias BOE), or BANK_OF_JAPAN (alias BOJ).

Optionally specify dateOrPeriod:

For US_CPI, US_PCE, and US_NONFARM_PAYROLLS: 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.

Input Schema

TableJSON Schema

Name	Required	Description
`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), 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, and US_NONFARM_PAYROLLS) or statement date (YYYY-MM-DD for central banks). If omitted, the latest event is returned.

Output Schema

TableJSON 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.

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

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds meaningful behavioral context beyond that: calculations are strictly deterministic and mathematical, and the tool explicitly provides no trading recommendations or predictive signals.

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 longer than average but every sentence earns its place: it front-loads the purpose, then parameter rules, then output fields. The structure is scannable and contains no fluff.

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?

Covers all call inputs, default behavior, supported date formats, and the returned metric fields. Since an output schema exists, detailed return-value documentation is not required; nothing important for correct invocation is missing.

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

Parameters4/5

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

The input schema already covers all three parameters with 100% coverage. The description adds value by giving canonical aliases (PCE/NFP/BOE/BOJ), concrete YYYY-MM vs YYYY-MM-DD examples, and the EURUSD default, though it largely reinforces schema information.

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?

Opens with a specific verb and object—'Retrieve deterministic post-event market reaction metrics'—and enumerates supported event types. Clear enough to distinguish from siblings like get_event_context and get_historical_reaction_context because it targets quantitative reaction metrics, not context or analogs.

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?

Explains exactly how to set targetType and dateOrPeriod per event family, including format and defaulting behavior. It does not explicitly name sibling alternatives or state when not to use this tool, so it stops 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 FX Context 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.

Resources

Need Help?