Skip to main content
Glama

FXMacroData

by io.github.fxmacrodata
OverviewDiscussionsAdmin

Commodities Visual Artifact

commodities_visual_artifact
Read-only

Same payload as commodities, but packaged with MCP Apps chart metadata so compatible clients render an interactive commodity chart inline. Access: requires an FXMacroData API key; an anonymous call returns subscription_required with a subscribe link.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_dateNoInclusive upper bound, YYYY-MM-DD.
indicatorYesCommodity indicator slug. Supported: crude_oil_inventories, gold, natural_gas, natural_gas_storage, oil_brent, oil_wti, platinum, silver.
start_dateNoInclusive lower bound, YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / end_date / title
      Removed value: -"End Date"
    • removedInput schema / properties / indicator / title
      Removed value: -"Indicator"
    • removedInput schema / properties / start_date / title
      Removed value: -"Start Date"
  2. Changed2 schema fields changed
    • changedInput schema / properties / indicator / description
      Previous value: -"Commodity indicator slug. Supported: gold, natural_gas, oil_brent, oil_wti, platinum, silver."New value: +"Commodity indicator slug. Supported: crude_oil_inventories, gold, natural_gas, natural_gas_storage, oil_brent, oil_wti, platinum, silver."
    • changedInput schema / properties / indicator / examples
      Previous value: -[
-  "gold",
-  "natural_gas",
-  "oil_brent",
-  "oil_wti",
-  "platinum",
-  "silver"
-]New value: +[
+  "crude_oil_inventories",
+  "gold",
+  "natural_gas",
+  "natural_gas_storage",
+  "oil_brent",
+  "oil_wti"
+]
  3. Changed2 schema fields changed
    • changedInput schema / properties / indicator / description
      Previous value: -"Commodity indicator slug. Supported: gold, platinum, silver."New value: +"Commodity indicator slug. Supported: gold, natural_gas, oil_brent, oil_wti, platinum, silver."
    • changedInput schema / properties / indicator / examples
      Previous value: -[
-  "crude_oil",
-  "natural_gas",
-  "gold",
-  "silver",
-  "copper"
-]New value: +[
+  "gold",
+  "natural_gas",
+  "oil_brent",
+  "oil_wti",
+  "platinum",
+  "silver"
+]
  4. Added

TDQS

A4.5/5.0
Behavior5/5

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

Discloses access requirements: requires an FXMacroData API key, and anonymous calls return subscription_required with a subscribe link. This is specific and consistent with the readOnlyHint annotation, adding valuable behavioral detail not present in the annotations.

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?

Two sentences, no redundancy, front-loads the key differentiator (chart metadata) and includes the access caveat. Every sentence adds value without unnecessary detail.

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?

For a simple tool with no output schema and three well-documented parameters, the description sufficiently explains the purpose, relationship to the sibling tool, and access constraints. Nothing essential is missing.

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 already documents all three parameters with descriptions and examples, covering 100% of parameters. The description adds no additional parameter semantics beyond referencing the same payload as commodities, so baseline score of 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?

Clearly states it returns the same payload as commodities but adds chart metadata for interactive rendering, differentiating from the commodities sibling tool. The verb 'packaged' implies retrieval and presentation, making the purpose unambiguous.

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?

Explicitly references the commodities sibling and notes the packaging difference, implying use when an interactive chart is desired instead of raw data. It also mentions access requirements, but does not explicitly name alternative tools like latest_commodities or provide a direct 'use when' construction.

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