Skip to main content
Glama

Stratalize Intelligence

Get Commodity Benchmark

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.7/5.0
Behavior4/5

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

Beyond the annotations (readOnly/openWorld/non-destructive), the description discloses genuinely useful behavior: the FRED provenance, daily update cadence, the x402 price of $0.10 USDC per call, and the no-charge 503 failure mode when upstream data is unavailable. It loses a point for stating the 503 behavior twice in near-identical wording rather than using the space for other traits.

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?

It is front-loaded with the strongest content first, but the pipe-delimited, fragment-heavy style litters it with redundant material: the HTTP 503 / no-charge condition appears twice, and pricing SLA text is interleaved with data description. Trimming the duplicate would make it tighter without losing 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 must convey what comes back, and it does specify price changes, an inflation signal, and a data_source provenance field (fred_api/fred_csv/fred_mixed). For a zero-required-parameter read tool with annotations already covering safety, that is close to sufficient, though the response shape is not described structurally.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter has 0% schema description coverage, so the description carries the burden; it partially compensates by listing covered commodities that map onto the energy/metals/agriculture enum values (and 'all' by implication). It never explicitly states that the category parameter filters results or what the default is when omitted, leaving a residual 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 opens with a specific verb+resource ('Live commodity price benchmarks') and enumerates the covered series (WTI, natural gas, gold, copper, wheat, soybeans) plus derived fields (weekly/monthly change, inflation pressure signal). It does not, however, differentiate itself from overlapping siblings such as get_agricultural_commodity_benchmark or get_copper_price_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?

Usage is only implied: 'For traders and macro analysts' names an audience, and 'inflation pressure signal' hints at the macro use case, but there is no explicit when-to-use, when-not-to-use, or pointer to a narrower sibling for single-commodity queries. An agent must infer that a broader 'all' pull is available versus the per-commodity tools.

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