mcp-livedatapro

getCommodityPrices

Live spot and futures prices for industrial metals, lumber, energy, and agricultural raw materials. Use when querying global wholesale spot and futures benchmark prices (LME, COMEX, CME, ICE) for raw materials, industrial metals, energy, and agriculture in USD. Do not use for retail gas station pump prices (use getFuelPrices) or company stock tickers (use getStockEodPrices).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "commodity": "<commodity>"
    },
    "name": "getCommodityPrices"
  }
}

Input Schema

Name	Required	Description	Default
`commodity`	Yes	Standardized raw material or commodity benchmark identifier.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 24, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / commodity / enum

Added value: +[
+  "gold",
+  "silver",
+  "copper",
+  "steel",
+  "lithium",
+  "aluminum",
+  "brent_oil",
+  "wti_oil",
+  "natural_gas",
+  "lumber",
+  "wheat",
+  "corn",
+  "coffee"
+]

addedInput schema / properties / commodity / examples
```
Added value: +[
+  "copper"
+]
```

Changed1 schema field changedOct 24, 2026

changedInput schema / properties / commodity / description

Previous value: -"Commodity name or ticker (e.g., steel, copper, lithium, lumber, brent_oil, wheat, gold)"New value: +"Standardized raw material or commodity benchmark identifier."

First observedOct 21, 2026

TDQS

A4.2/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It does disclose valuable traits: liveness ('Live'), the quoting venues (LME, COMEX, CME, ICE), and the currency (USD). However it never states units of quote (per tonne vs. per troy ounce), update frequency, or whether a single point or a curve is returned — significant gaps for a commodity price feed.

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?

Three tight sentences: what it returns, when to use it, when not to. The core purpose is front-loaded and every clause carries selection-relevant 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?

For a one-parameter read-only lookup with no output schema and no annotations, the description is nearly sufficient for correct invocation and routing. The remaining gap is return-side detail (units, whether futures curves or single quotes are returned), which matters for interpreting commodity prices.

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 coverage is 100% and the enum already constrains the single parameter to 13 standardized values with its own description, so the schema does the heavy lifting. The description's category list (metals, energy, agriculture, lumber) loosely maps to the enum but adds no syntax or format guidance beyond it.

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?

Names the specific resource (live spot and futures prices) and its domain (industrial metals, lumber, energy, agricultural raw materials), which separates it from every pricing sibling in the list. The verb+resource combination is unambiguous.

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

Usage Guidelines5/5

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

Explicitly states when to use it (global wholesale benchmark prices from LME, COMEX, CME, ICE in USD) and names two alternatives with the condition that selects them: getFuelPrices for retail pump prices and getStockEodPrices for company tickers. Nothing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All mcp-livedatapro tools Inspect

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

Need Help?