Skip to main content
Glama

Stratalize Intelligence

Get Agricultural Commodity Benchmark

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

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety is covered. The description goes further by disclosing upstream provenance (FRED / IMF), the returned fields (price, unit, observation period), the nominal per-call cost, and an attestation/verification URL — all context an agent cannot get from annotations or schema. It loses a point only for repeating the $0.02 price twice in slightly different forms, which adds noise rather than clarity.

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 first two sentences are front-loaded and earn their place. The trailing marketing and attestation boilerplate occupies roughly half the text, and '$0.02 atomic' followed later by '$0.02 USDC per call' is a straight duplication that dilutes the useful content.

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 return-value burden and does so by naming USD price, unit, and observation period. Combined with source attribution and cost disclosure, an agent has what it needs to call and interpret the result, with only minor gaps such as update frequency or historical coverage.

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%, but the single parameter is a closed enum of five values that the schema itself fully constrains, and the description restates exactly those five commodities. That confirms the domain but adds no meaning about units, quoting conventions, or historical depth for the chosen commodity. With one enumerated parameter, this is adequate but not additive.

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?

States a specific verb and resource: 'Spot agricultural commodity price from FRED IMF primary commodity series,' and enumerates the five covered crops. That scope distinguishes it reasonably well from a generic commodity benchmark sibling, though it never explicitly contrasts itself with get_commodity_benchmark, so the differentiation is inferred rather than stated.

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 phrase 'for crop hedging, food cost modeling, and trade exposure agents' implies the domain and audience for which the tool is appropriate, giving implied usage. There is no explicit when-not-to-use guidance, no mention of prerequisites such as API keys or rate limits, and no named alternative for non-agricultural commodities or futures data.

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