Skip to main content
Glama

FXMacroData

by io.github.fxmacrodata
OverviewDiscussionsAdmin

COT Report

cot_data
Read-only

Get weekly CFTC Commitment of Traders (COT) positioning data for a currency's FX futures contract on the CME. Use this when the user asks about speculator positioning, non-commercial longs vs shorts, hedge-fund FX positioning, or wants to gauge sentiment extremes. Returns weekly snapshots with long/short open interest by trader category. Updated every Friday at 15:30 ET reflecting the Tuesday cutoff. Requires an API key. Supported currencies: AUD, CAD, CHF, EUR, GBP, JPY, MXN, NZD, USD, XAU. 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 for the FX futures contract (case-insensitive). Supported: AUD, CAD, CHF, EUR, GBP, JPY, MXN, NZD, USD, XAU.
end_dateNoInclusive upper bound, YYYY-MM-DD.
start_dateNoInclusive lower bound, YYYY-MM-DD.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / currency / title
      Removed value: -"Currency"
    • removedInput schema / properties / end_date / title
      Removed value: -"End Date"
    • removedInput schema / properties / start_date / title
      Removed value: -"Start Date"
  2. Changed1 schema field changed
    • changedInput schema / properties / currency / description
      Previous value: -"3-letter ISO currency code for the FX futures contract (case-insensitive). Supported: AUD, CAD, CHF, EUR, GBP, HUF, JPY, MXN, NZD, TRY, USD, XAU."New value: +"3-letter ISO currency code for the FX futures contract (case-insensitive). Supported: AUD, CAD, CHF, EUR, GBP, JPY, MXN, NZD, USD, XAU."
  3. Changed1 schema field changed
    • changedInput schema / properties / currency / description
      Previous value: -"3-letter ISO currency code for the FX futures contract (case-insensitive). Supported: AUD, CAD, CHF, EUR, GBP, HUF, JPY, MXN, NZD, TRY, USD."New value: +"3-letter ISO currency code for the FX futures contract (case-insensitive). Supported: AUD, CAD, CHF, EUR, GBP, HUF, JPY, MXN, NZD, TRY, USD, XAU."
  4. Changed1 schema field changed
    • changedInput schema / properties / currency / description
      Previous value: -"3-letter ISO currency code for the FX futures contract (case-insensitive). Supported: AUD, CAD, CHF, EUR, GBP, HUF, JPY, NZD, TRY, USD."New value: +"3-letter ISO currency code for the FX futures contract (case-insensitive). Supported: AUD, CAD, CHF, EUR, GBP, HUF, JPY, MXN, NZD, TRY, USD."
  5. Changed1 schema field changed
    • changedInput schema / properties / currency / description
      Previous value: -"3-letter ISO currency code for the FX futures contract (case-insensitive). Supported: AUD, CAD, CHF, EUR, GBP, HUF, JPY, MXN, NZD, TRY, USD."New value: +"3-letter ISO currency code for the FX futures contract (case-insensitive). Supported: AUD, CAD, CHF, EUR, GBP, HUF, JPY, NZD, TRY, USD."
  6. Changed6 schema fields changed
    • addedInput schema / properties / currency / description
      Added value: +"3-letter ISO currency code for the FX futures contract (case-insensitive). Supported: AUD, CAD, CHF, EUR, GBP, HUF, JPY, MXN, NZD, TRY, USD."
    • addedInput schema / properties / currency / examples
      Added value: +[
+  "eur",
+  "jpy",
+  "gbp",
+  "aud"
+]
    • addedInput schema / properties / end_date / description
      Added value: +"Inclusive upper bound, YYYY-MM-DD."
    • addedInput schema / properties / end_date / examples
      Added value: +[
+  "2020-01-01",
+  "2024-06-30"
+]
    • addedInput schema / properties / start_date / description
      Added value: +"Inclusive lower bound, YYYY-MM-DD."
    • addedInput schema / properties / start_date / examples
      Added value: +[
+  "2020-01-01",
+  "2024-06-30"
+]
  7. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond annotations (readOnlyHint=true, destructiveHint=false), the description adds update frequency (Friday 15:30 ET, Tuesday cutoff), weekly snapshot format, and API key requirement. It also discloses that anonymous calls return subscription_required, providing valuable behavioral context for the agent.

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 moderately long but well-organized: core function first, then usage scenarios, then update/API details, then supported currencies, then access note. Each sentence adds value, though the supported currency list could be seen as redundant with the schema. Overall front-loaded and efficient.

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?

With an output schema present and 3 simple parameters (1 required), the description covers the return format (weekly snapshots with long/short open interest), update schedule, API key requirement, and supported currencies. It provides everything an agent needs to decide and call correctly, including failure mode (subscription_required).

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 all parameters (currency, start_date, end_date) are already documented in the schema. The description adds supported currency list and case-insensitivity, but these are also in the schema, so it does not add meaningful new meaning beyond the schema.

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 clearly states the tool fetches weekly CFTC COT positioning data for FX futures on CME, specifying the resource and action. It distinguishes itself from siblings like cot_visual_artifact (visual) and forex (broader data) by focusing on positioning metrics and trader categories.

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 lists use cases: speculator positioning, non-commercial longs vs shorts, hedge-fund positioning, sentiment extremes. It also notes API key requirement and that anonymous calls return subscription_required, but does not explicitly name alternative tools for other data types, so it's clear on when to use but lacks explicit exclusions.

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