Skip to main content
Glama

FXMacroData

by io.github.fxmacrodata
OverviewDiscussionsAdmin

Macro Briefing Task

macro_briefing_task
Read-only

Build a compact macro briefing for a currency by combining catalogue, key macro series, release-calendar, prediction, news, risk-sentiment, COT, seasonality, and FX technical context. Supports MCP Tasks for async execution when clients send a task-augmented request. Access: requires an FXMacroData API key; an anonymous call returns subscription_required with a subscribe link.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
currencyYes3-letter ISO currency 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / currency / description
      Previous value: -"3-letter ISO currency code (case-insensitive). Supported: AUD, BRL, CAD, CHF, CNH, CNY, DKK, EUR, GBP, ILS, JPY, NGN, NOK, NZD, PEN, SEK, THB, USD."New value: +"3-letter ISO currency 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. Changed1 schema field changed
    • removedInput schema / properties / currency / title
      Removed value: -"Currency"
  3. Changed1 schema field changed
    • changedInput schema / properties / currency / description
      Previous value: -"3-letter ISO currency 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: +"3-letter ISO currency code (case-insensitive). Supported: AUD, BRL, CAD, CHF, CNH, CNY, DKK, EUR, GBP, ILS, JPY, NGN, NOK, NZD, PEN, SEK, THB, USD."
  4. Changed1 schema field changed
    • changedInput schema / properties / currency / description
      Previous value: -"3-letter ISO currency code (case-insensitive). Supported: AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, NGN, NOK, NZD, PEN, SEK, THB, USD."New value: +"3-letter ISO currency code (case-insensitive). Supported: AUD, BRL, CAD, CHF, CNH, CNY, DKK, EUR, GBP, IDR, ILS, JPY, NGN, NOK, NZD, PEN, SEK, THB, USD."
  5. Changed1 schema field changed
    • changedInput schema / properties / currency / description
      Previous value: -"3-letter ISO currency code (case-insensitive). Supported: AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, NGN, NZD, PEN, SEK, THB, USD."New value: +"3-letter ISO currency code (case-insensitive). Supported: AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, NGN, NOK, NZD, PEN, SEK, THB, USD."
  6. Changed1 schema field changed
    • changedInput schema / properties / currency / description
      Previous value: -"3-letter ISO currency code (case-insensitive). Supported: AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, NZD, PEN, SEK, THB, USD."New value: +"3-letter ISO currency code (case-insensitive). Supported: AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, NGN, NZD, PEN, SEK, THB, USD."
  7. Changed1 schema field changed
    • changedInput schema / properties / currency / description
      Previous value: -"3-letter ISO currency code (case-insensitive). Supported: AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, NZD, PEN, SEK, USD."New value: +"3-letter ISO currency code (case-insensitive). Supported: AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, NZD, PEN, SEK, THB, USD."
  8. Changed1 schema field changed
    • changedInput schema / properties / currency / description
      Previous value: -"3-letter ISO currency 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: +"3-letter ISO currency code (case-insensitive). Supported: AUD, BRL, CAD, CHF, CNH, DKK, EUR, GBP, IDR, ILS, JPY, NZD, PEN, SEK, USD."
  9. Changed1 schema field changed
    • changedInput schema / properties / currency / description
      Previous value: -"3-letter ISO currency 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: +"3-letter ISO currency 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. Changed1 schema field changed
    • changedInput schema / properties / currency / description
      Previous value: -"3-letter ISO currency code (case-insensitive). Supported: AED, ARS, AUD, BOB, BRL, CAD, CHF, CLP, COP, CZK, DKK, DZD, EGP, EUR, GBP, HKD, HUF, IDR, ILS, INR, JPY, MAD, MXN, MYR, NGN, NOK, NZD, PEN, PHP, PKR, PLN, RUB, SAR, SEK, THB, TRY, TWD, USD, UYU, VND."New value: +"3-letter ISO currency code (case-insensitive). Supported: AED, AUD, BRL, CAD, CHF, DKK, EUR, GBP, IDR, ILS, JPY, MXN, NZD, PEN, PLN, SEK, THB, TWD, USD."
  11. Changed1 schema field changed
    • changedInput schema / properties / currency / description
      Previous value: -"3-letter ISO currency code (case-insensitive). Supported: AED, ARS, AUD, BOB, BRL, CAD, CHF, CLP, COP, CZK, DKK, DZD, EGP, EUR, GBP, HKD, HUF, IDR, ILS, INR, JPY, MAD, MXN, MYR, NGN, NOK, NZD, PEN, PHP, PKR, PLN, RUB, SAR, SEK, SGD, THB, TRY, TWD, USD, UYU, VND, ZAR."New value: +"3-letter ISO currency code (case-insensitive). Supported: AED, ARS, AUD, BOB, BRL, CAD, CHF, CLP, COP, CZK, DKK, DZD, EGP, EUR, GBP, HKD, HUF, IDR, ILS, INR, JPY, MAD, MXN, MYR, NGN, NOK, NZD, PEN, PHP, PKR, PLN, RUB, SAR, SEK, THB, TRY, TWD, USD, UYU, VND."
  12. Changed1 schema field changed
    • changedInput schema / properties / currency / description
      Previous value: -"3-letter ISO currency code (case-insensitive). Supported: AED, ARS, AUD, BOB, BRL, CAD, CHF, CLP, COP, CZK, DKK, DZD, EGP, EUR, GBP, HKD, HUF, IDR, ILS, INR, ISK, JPY, MAD, MXN, MYR, NGN, NOK, NZD, PEN, PHP, PKR, PLN, RUB, SAR, SEK, SGD, THB, TRY, TWD, USD, UYU, VND, ZAR."New value: +"3-letter ISO currency code (case-insensitive). Supported: AED, ARS, AUD, BOB, BRL, CAD, CHF, CLP, COP, CZK, DKK, DZD, EGP, EUR, GBP, HKD, HUF, IDR, ILS, INR, JPY, MAD, MXN, MYR, NGN, NOK, NZD, PEN, PHP, PKR, PLN, RUB, SAR, SEK, SGD, THB, TRY, TWD, USD, UYU, VND, ZAR."
  13. Changed1 schema field changed
    • changedInput schema / properties / currency / description
      Previous value: -"3-letter ISO currency code (case-insensitive). Supported: AED, ARS, AUD, BOB, BRL, CAD, CHF, CLP, COP, CZK, DKK, DZD, EGP, EUR, GBP, HKD, HUF, IDR, ILS, INR, JPY, MAD, MXN, MYR, NGN, NOK, NZD, PEN, PHP, PKR, PLN, RUB, SAR, SEK, SGD, THB, TRY, TWD, USD, UYU, VND, ZAR."New value: +"3-letter ISO currency code (case-insensitive). Supported: AED, ARS, AUD, BOB, BRL, CAD, CHF, CLP, COP, CZK, DKK, DZD, EGP, EUR, GBP, HKD, HUF, IDR, ILS, INR, ISK, JPY, MAD, MXN, MYR, NGN, NOK, NZD, PEN, PHP, PKR, PLN, RUB, SAR, SEK, SGD, THB, TRY, TWD, USD, UYU, VND, ZAR."
  14. Changed1 schema field changed
    • changedInput schema / properties / currency / description
      Previous value: -"3-letter ISO currency code (case-insensitive). Supported: AED, ARS, AUD, BOB, BRL, CAD, CHF, CLP, COP, CZK, DKK, DZD, EGP, EUR, GBP, HKD, HUF, IDR, ILS, INR, JPY, MAD, MYR, NGN, NOK, NZD, PEN, PHP, PKR, PLN, RUB, SAR, SEK, SGD, THB, TRY, TWD, USD, UYU, VND, ZAR."New value: +"3-letter ISO currency code (case-insensitive). Supported: AED, ARS, AUD, BOB, BRL, CAD, CHF, CLP, COP, CZK, DKK, DZD, EGP, EUR, GBP, HKD, HUF, IDR, ILS, INR, JPY, MAD, MXN, MYR, NGN, NOK, NZD, PEN, PHP, PKR, PLN, RUB, SAR, SEK, SGD, THB, TRY, TWD, USD, UYU, VND, ZAR."
  15. Changed1 schema field changed
    • changedInput schema / properties / currency / description
      Previous value: -"3-letter ISO currency code (case-insensitive). Supported: AED, ARS, AUD, BOB, BRL, CAD, CHF, CLP, CNH, COP, CZK, DKK, DZD, EGP, EUR, GBP, HKD, HUF, IDR, ILS, INR, JPY, MAD, MXN, MYR, NGN, NOK, NZD, PEN, PHP, PKR, PLN, RUB, SAR, SEK, SGD, THB, TRY, TWD, USD, UYU, VND, ZAR."New value: +"3-letter ISO currency code (case-insensitive). Supported: AED, ARS, AUD, BOB, BRL, CAD, CHF, CLP, COP, CZK, DKK, DZD, EGP, EUR, GBP, HKD, HUF, IDR, ILS, INR, JPY, MAD, MYR, NGN, NOK, NZD, PEN, PHP, PKR, PLN, RUB, SAR, SEK, SGD, THB, TRY, TWD, USD, UYU, VND, ZAR."
  16. Changed1 schema field changed
    • changedInput schema / properties / currency / description
      Previous value: -"3-letter ISO currency code (case-insensitive). Supported: AUD, BRL, CAD, CHF, DKK, EUR, GBP, JPY, NZD, PEN, PLN, SEK, SGD, USD."New value: +"3-letter ISO currency code (case-insensitive). Supported: AED, ARS, AUD, BOB, BRL, CAD, CHF, CLP, CNH, COP, CZK, DKK, DZD, EGP, EUR, GBP, HKD, HUF, IDR, ILS, INR, JPY, MAD, MXN, MYR, NGN, NOK, NZD, PEN, PHP, PKR, PLN, RUB, SAR, SEK, SGD, THB, TRY, TWD, USD, UYU, VND, ZAR."
  17. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context: it supports async MCP Tasks, requires an API key, and returns subscription_required with a subscribe link for anonymous calls. This goes beyond the annotations and helps the agent anticipate failure modes. It does not detail output format, but with no output schema and a briefing-builder tool, the description carries the burden reasonably well.

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?

The description is compact and front-loaded with the core purpose, then adds async support and access requirements in two additional sentences. Every sentence earns its place, though the access sentence could arguably be moved to annotations or a separate auth field. Still, it is appropriately sized and well-structured.

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 single-parameter briefing tool with read-only annotations, the description covers the purpose, data sources, async behavior, and auth failure mode. It does not describe the output structure or how the briefing is delivered (e.g., text vs artifact), but given the tool's complexity and the absence of an output schema, the description is reasonably complete. A 5 would require explicit output format or delivery details.

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 the single 'currency' parameter with examples and a supported list. The description adds that the briefing is 'for a currency' but does not add syntax, formatting, or behavioral details beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific verb ('Build') and resource ('compact macro briefing for a currency'), and enumerates the exact data domains combined (catalogue, key macro series, release-calendar, prediction, news, risk-sentiment, COT, seasonality, FX technical). This clearly distinguishes it from sibling tools like macro_war_room_task or macro_research_pack_task, which likely produce different briefing scopes.

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 explicitly mentions MCP Tasks support for async execution when clients send a task-augmented request, which is a clear usage condition. It also states the access requirement (FXMacroData API key) and the anonymous-call fallback. However, it does not explicitly name sibling alternatives or state when NOT to use this tool versus other briefing tasks, so it falls just 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 FXMacroData toolsInspect
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