Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Commodity prices: gold, oil, silver, gas, grains

commodity_price
Read-only

Commodity price now for gold, silver, platinum, palladium, copper, crude oil (WTI and Brent), natural gas, gasoline, heating oil, corn, wheat, soybeans, coffee, sugar, cocoa or cotton: the front-month futures price with its unit, the day's change and percent, previous close, day range and 52-week range. XAU, oil and similar names work. Use to price a commodity in an agent, track inflation inputs, or add market context to a brief. Example: commodity=gold. Price $0.001/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": "commodity_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
commodityYesOne of: gold, silver, platinum, palladium, copper, crude-oil, brent, natural-gas, gasoline, heating-oil, corn, wheat, soybeans, coffee, sugar, cocoa, cotton

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the cost model, payment methods, first-25-free allowance, failed-call charging, and that repeated calls are not free. It also states the tool reads or computes only and changes nothing, which is consistent with the readOnlyHint annotation. Remaining gaps are minor, such as data freshness or market-hours behavior.

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

Conciseness4/5

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

The description is front-loaded with the core purpose and returned fields, and most sentences carry useful information. It is a dense paragraph with a long commodity enumeration, but the length is largely justified by the amount of behavioral and billing 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?

The tool has one required parameter, no output schema, and simple annotations. The description covers the resource, returned fields, aliases, examples, use cases, cost behavior, and non-mutating nature, leaving little an agent needs to infer before calling it.

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?

Schema coverage is 100%, so the schema already carries the baseline. The description adds useful meaning by saying aliases such as XAU and oil work and by giving an example call, commodity=gold.

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?

The description names a specific resource and scope: current commodity prices across enumerated metals, energy, and agricultural commodities, with the returned futures price and related market fields. It clearly distinguishes itself from crypto and FX siblings by explicitly framing the tool around commodities.

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?

It gives concrete use cases such as pricing a commodity in an agent, tracking inflation inputs, and adding market context. It does not explicitly exclude alternatives like bitcoin_price or fx, but the commodity scope is clear enough for an agent to select it correctly.

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.