Skip to main content
Glama

get_commodity_benchmark

Read-only

Live commodity price benchmarks — WTI crude, natural gas, gold, copper, wheat, soybeans. Weekly and monthly price changes, inflation pressure signal. Source: FRED. Updated daily. For traders and macro analysts. Live source. Returns HTTP 503 (no charge) if upstream source unavailable for >50% of fields. | x402 SLA: $0.10 USDC per call. Returns HTTP 503 (no charge) when upstream data sources unavailable. data_source field discloses provenance (fred_api/fred_csv/fred_mixed).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_commodity_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, but the description adds substantial information beyond them: the upstream source (FRED), daily refresh cadence, the failure mode (HTTP 503 with no charge when upstream is unavailable for >50% of fields), the cost model ($0.10 USDC per call via x402), and the provenance disclosure through a data_source field (fred_api/fred_csv/fred_mixed). Pricing and error semantics are exactly the kind of behavior annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The failure behavior is stated twice ('Returns HTTP 503 (no charge) if upstream source unavailable for >50% of fields' and again 'Returns HTTP 503 (no charge) when upstream data sources unavailable'), and 'Live source' redundantly repeats 'Live commodity...'. The pipe-delimited run-on structure buries the useful pricing and provenance details rather than front-loading them.

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?

There is no output schema, so the description carries the burden of describing returns, and it does so partially: weekly and monthly price changes, an inflation pressure signal, and a data_source provenance field are all named. Combined with a one-parameter schema, an agent has enough to call the tool correctly, though the omitted-category default and the shape of the per-commodity records remain unspecified.

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 0% for the single optional 'category' parameter, so the description would ideally explain it. It does not reference the parameter at all, but the enum values (energy, metals, agriculture, all) are largely self-documenting and the listed commodities map onto them. The default behavior when 'category' is omitted remains unstated, which is a real gap.

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 names a specific verb-and-resource pairing ('Live commodity price benchmarks') and enumerates the covered assets (WTI crude, natural gas, gold, copper, wheat, soybeans) plus the derived metrics (weekly/monthly price changes, inflation pressure signal). This clearly separates it from unrelated siblings like get_aml_regulatory_benchmark or get_chain_tvl_benchmark. It does not, however, explicitly route away from the closely overlapping siblings get_gas_benchmark, get_copper_price_benchmark, and get_agricultural_commodity_benchmark.

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?

'For traders and macro analysts' implies an audience and therefore an implied usage context, which is enough to infer the tool is for market/macro analysis. But there is no explicit when-to-use statement, no exclusion, and no mention of how it relates to the single-commodity sibling benchmarks. The agent must infer selection from the commodity list alone.

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.

Resources