Skip to main content
Glama

Primary Source Commodities

Cash Grain Bids and Basis

cash.bids
Read-onlyIdempotent

A country elevator's cash bid for physical grain, from USDA AMS daily cash grain bid reports, searched across every state report at once — which AMS itself cannot do, because MARS is report-centric with no commodity-wide search. Returns basis in CENTS per bushel against a named futures month, price in DOLLARS per bushel, location, grade, elevator class, freight and delivery. THIS IS NOT a futures settlement and NOT the NASS season-average price received that price.latest returns for ZC/ZW/ZS; all three are correct and all three differ. Values are ranges where the report published a range. Latest published print only — there is no stored history, so this cannot tell you whether basis is strengthening; read each row's basis_change, which is the agency's own answer. Wheat must name its class: CBOT soft red winter, KCBT hard red winter and MGE hard red spring traded 35 cents apart on the same page. Paid.

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": "cash.bids"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum rows.
monthNoFutures month code ("Z") or contract ("2026-12") the basis is quoted against.
stateNoTwo-letter state code, e.g. IA.
commodityYesWhich grain. Required.
include_staleNoInclude reports that have not published recently. Excluded and named by default.
elevator_classNoNarrow to one kind of buyer.

Output Schema

NameRequiredDescriptionDefault
bidsYesCash bid rows, widest basis first
notesYes
commodityYes
instrumentNoCatalog instrument where one quotes this class; null is a real answer
reports_searchedYes
stale_reports_excludedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive, but the description adds substantive behavior: latest print only with no stored history, values returned as ranges when the report published a range, units differentiated (basis in cents, price in dollars), and a note that it is 'Paid' (quota-consuming). That is real context beyond the structured fields.

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?

Dense but front-loaded: the core identity arrives in the first clause, then scope, then disambiguation, then return semantics. Every sentence carries distinct information despite the em-dash packing.

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?

Output schema exists, yet the description still summarizes the meaningful return fields (basis, price, location, grade, elevator class, freight, delivery) and warns there is no history so basis_change is the way to read trend. For a six-parameter tool with rich annotations, nothing an agent needs to call it correctly is missing.

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 baseline is 3, and the description earns above that: it explains why the commodity enum splits wheat into classes (CBOT/KCBT/MGE traded 35 cents apart on the same page) and clarifies that month is the futures month the basis is quoted against. It adds genuine meaning rather than repeating the schema.

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: an elevator's cash bid for physical grain pulled from USDA AMS daily reports, searched across all state reports at once. It also explicitly distinguishes itself from price.latest and the NASS season-average price, so an agent can differentiate it from siblings without opening any schema.

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?

Explicitly fences off two wrong interpretations ('NOT a futures settlement', 'NOT the NASS season-average price received that price.latest returns') and clarifies that wheat must name its class. It stops short of naming alternatives for the cases it disclaims (e.g., pointing to a history tool for trend analysis), leaving that inference to the agent.

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