Skip to main content
Glama

get_agricultural_commodity_benchmark

Read-only

Spot agricultural commodity price from FRED IMF primary commodity series for soybeans, wheat, corn, cotton, or coffee. Returns USD price, unit, and observation period for crop hedging, food cost modeling, and trade exposure agents. Source: FRED / IMF. $0.02 atomic. Cryptographically attested with a post-quantum signed settlement receipt. Verify at trust.stratalize.com/verify. $0.02 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault
commodityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, non-destructive, and open-world behavior, and the description adds material beyond them: the upstream source (FRED / IMF), the returned fields (price, unit, observation period), per-call cost, and a verifiable signed settlement receipt with a verify URL. The repeated cost statement ("$0.02 atomic" and "$0.02 USDC per call") is the only real shortfall.

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 core purpose is front-loaded and the sentence structure is clean, but the pricing is stated twice in different phrasings ("$0.02 atomic" and "$0.02 USDC per call"), and the attestation/verify-URL block sits mid-description, splitting the economic and trust information awkwardly.

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 correctly carries the return-value burden by naming price, unit, and observation period, and adds source and trust/verification context. It stops short of describing freshness, lag, or update cadence, which matters for a spot-price benchmark but is not fatal.

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, but the description compensates by listing all five accepted commodity values, matching the enum exactly. It adds no further detail (e.g., is `commodity` case-sensitive, what unit basis is returned per crop), but for a one-param tool this is close to sufficient.

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?

States a specific verb and resource ("Spot agricultural commodity price from FRED IMF primary commodity series") and enumerates the exact supported crops, which makes its scope distinguishable from the generic get_commodity_benchmark sibling. An agent can tell what this returns without opening the schema.

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?

The description names consumer contexts (crop hedging, food cost modeling, trade exposure agents), which implies intended use, but never states when to prefer this over get_commodity_benchmark or any other benchmark sibling, nor any prerequisites or exclusions.

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