Skip to main content
Glama

FXMacroData

by io.github.fxmacrodata
OverviewDiscussionsAdmin

Commodities Visual Artifact

commodities_visual_artifact
Read-only

Returns commodity price history 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

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower. The description still adds real behavioral context beyond them: it requires an FXMacroData API key and an anonymous call returns 'subscription_required' with a subscribe link, which is exactly the kind of failure-mode disclosure an agent needs.

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 padding, and the primary purpose (return commodity history with inline chart metadata) is front-loaded ahead of the secondary access caveat. Every clause carries information.

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?

With no output schema, the description carries the return-value burden and does so partially: it says the result is price history plus chart metadata for compatible clients. Combined with full schema coverage and explicit auth behavior, an agent has enough to call it correctly, though the response shape is only sketched.

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%, with each of the three parameters (indicator, start_date, end_date) fully documented including examples and the supported indicator slugs, so the baseline is 3. The description adds nothing about parameter syntax or semantics beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Returns commodity price history') plus a distinctive capability ('MCP Apps chart metadata ... render an interactive commodity chart inline'), which implicitly separates it from the plain-data sibling 'commodities' and from other visual artifacts. It does not explicitly name a sibling, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the agent can infer it should pick this over 'commodities' when an inline chart is wanted, but the description never says when to choose this versus 'commodities', 'cot_visual_artifact', or other chart tools. The access note about API keys is useful but is about authorization, not tool selection.

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