Skip to main content
Glama

Policy Scenario Modeler Task

policy_scenario_modeler_task
Read-only

Run a policy-rate spread what-if scenario for an FX pair and estimate directional spot impact using an explicit heuristic elasticity assumption. Supports MCP Tasks for async execution when clients send task-augmented requests. Access: requires an FXMacroData API key; an anonymous call returns subscription_required with a subscribe link.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
baseYesBase currency, 3-letter ISO code (case-insensitive). Supported: AUD, BRL, CAD, CHF, CNH, CNY, DKK, EUR, GBP, HUF, ILS, JPY, KRW, MYR, NGN, NOK, NZD, PEN, SEK, THB, TWD, USD.
quoteYesQuote currency, 3-letter ISO code (case-insensitive). Supported: AUD, BRL, CAD, CHF, CNH, CNY, DKK, EUR, GBP, HUF, ILS, JPY, KRW, MYR, NGN, NOK, NZD, PEN, SEK, THB, TWD, USD.
end_dateNoOptional inclusive upper bound, YYYY-MM-DD.
shock_bpsNoPolicy shock size in basis points (100 bps = 1.00 percentage point).
shock_legNoWhich leg receives the policy shock: base or quote.base
start_dateNoOptional inclusive lower bound, YYYY-MM-DD.
policy_shock_bpsNoOptional alias for shock_bps for compatibility with host-side app payloads.
elasticity_per_100bpsNoHeuristic percent change in FX spot for a 100 bps spread change. Used as a scenario assumption, not a forecast guarantee.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / base / description
      Previous value: -"Base currency, 3-letter ISO code (case-insensitive). 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 (case-insensitive). 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 (case-insensitive). 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 (case-insensitive). Supported: AUD, BRL, CAD, CHF, CNH, CNY, DKK, EUR, GBP, HUF, ILS, JPY, KRW, MYR, NGN, NOK, NZD, PEN, SEK, THB, TWD, USD."
  2. Changed8 schema fields changed
    • removedInput schema / properties / base / title
      Removed value: -"Base"
    • removedInput schema / properties / elasticity_per_100bps / title
      Removed value: -"Elasticity Per 100Bps"
    • removedInput schema / properties / end_date / title
      Removed value: -"End Date"
    • removedInput schema / properties / policy_shock_bps / title
      Removed value: -"Policy Shock Bps"
    • removedInput schema / properties / quote / title
      Removed value: -"Quote"
    • removedInput schema / properties / shock_bps / title
      Removed value: -"Shock Bps"
    • removedInput schema / properties / shock_leg / title
      Removed value: -"Shock Leg"
    • removedInput schema / properties / start_date / title
      Removed value: -"Start Date"
  3. Changed2 schema fields changed
    • changedInput schema / properties / base / description
      Previous value: -"Base currency, 3-letter ISO code (case-insensitive). 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 (case-insensitive). 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 (case-insensitive). 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 (case-insensitive). Supported: AUD, BRL, CAD, CHF, CNH, CNY, DKK, EUR, GBP, ILS, JPY, NGN, NOK, NZD, PEN, SEK, THB, USD."
  4. Changed2 schema fields changed
    • changedInput schema / properties / base / description
      Previous value: -"Base currency, 3-letter ISO code (case-insensitive). 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 (case-insensitive). 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 (case-insensitive). 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 (case-insensitive). Supported: AUD, BRL, CAD, CHF, CNH, CNY, DKK, EUR, GBP, IDR, ILS, JPY, NGN, NOK, NZD, PEN, SEK, THB, USD."
  5. Changed2 schema fields changed
    • changedInput schema / properties / base / description
      Previous value: -"Base currency, 3-letter ISO code (case-insensitive). 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 (case-insensitive). 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 (case-insensitive). 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 (case-insensitive). Supported: AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, NGN, NOK, NZD, PEN, SEK, THB, USD."
  6. Changed2 schema fields changed
    • changedInput schema / properties / base / description
      Previous value: -"Base currency, 3-letter ISO code (case-insensitive). 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 (case-insensitive). 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 (case-insensitive). 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 (case-insensitive). Supported: AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, NGN, NZD, PEN, SEK, THB, USD."
  7. Changed2 schema fields changed
    • changedInput schema / properties / base / description
      Previous value: -"Base currency, 3-letter ISO code (case-insensitive). Supported: AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, NZD, PEN, SEK, USD."New value: +"Base currency, 3-letter ISO code (case-insensitive). 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 (case-insensitive). Supported: AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, NZD, PEN, SEK, USD."New value: +"Quote currency, 3-letter ISO code (case-insensitive). Supported: AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, NZD, PEN, SEK, THB, USD."
  8. Changed2 schema fields changed
    • changedInput schema / properties / base / description
      Previous value: -"Base currency, 3-letter ISO code (case-insensitive). 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 (case-insensitive). 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 (case-insensitive). 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 (case-insensitive). Supported: AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, NZD, PEN, SEK, USD."
  9. Changed2 schema fields changed
    • changedInput schema / properties / base / description
      Previous value: -"Base currency, 3-letter ISO code (case-insensitive). 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 (case-insensitive). 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 (case-insensitive). 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 (case-insensitive). Supported: AED, AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, MXN, NZD, PEN, PLN, SEK, THB, TWD, USD."
  10. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint and destructiveHint annotations, the description discloses important behavioral details: async support for task-augmented requests, an API-key access requirement, the anonymous subscription_required response, and the heuristic nature of the elasticity assumption. This materially helps an agent anticipate outcomes and errors.

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?

Three sentences, each earning its place: the first states the core function, the second explains async capability, and the third covers authentication and failure behavior. The most important information is front-loaded.

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 an 8-parameter task tool with no output schema, the description covers the core behavior, auth requirement, anonymous failure mode, and async support. However, it does not describe the response/output format beyond 'estimate directional spot impact', which is a modest gap given there is no output schema.

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?

Since schema description coverage is 100%, the schema already documents all 8 parameters, including examples and defaults. The description adds thematic context ('policy-rate spread', 'elasticity') but no parameter-level meaning beyond what the schema provides. Baseline 3 is appropriate.

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?

The description uses a specific verb ('Run') with a precise resource ('policy-rate spread what-if scenario for an FX pair') and the distinctive outcome ('estimate directional spot impact using an explicit heuristic elasticity assumption'). This clearly differentiates the tool from sibling tasks like fx_backtest_task or rate_differentials, even without naming them.

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?

The description provides clear usage context: it is for scenario modeling, supports async execution via MCP Tasks, and requires an FXMacroData API key, including the anonymous failure mode. However, it does not explicitly name alternatives or state when not to use this tool versus sibling task tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.