Skip to main content
Glama

Primary Source Commodities

AMS Cash Grain Report Index

cash.reports
Read-onlyIdempotent

Which USDA AMS daily cash grain bid reports exist, which state and commodities each covers, and how fresh each is. FREE. Call before cash.bids to learn which states are covered and which reports have stopped publishing: liveness is current, stale (served and flagged), unlisted (AMS no longer lists it) or unknown. Three reports are published as covered-but-unparsed rather than omitted, because a visible gap beats a silent absence.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cash.reports"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
reportsYesPer report: slug, state, commodities, as_of, liveness
report_countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, the description adds material behavioral context: the tool is free, liveness values are defined (current, stale, unlisted, unknown), and covered-but-unparsed reports are intentionally visible rather than omitted. These details help an agent interpret both the index content and gaps in coverage.

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?

The description is short and front-loaded: the first sentence defines the returned index, the second gives the key usage instruction and liveness taxonomy, and the third explains the covered-but-unparsed exception. Every sentence contributes useful information without repetition.

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?

Because an output schema exists, the description does not need to enumerate return fields, and it instead supplies the interpretive context an agent needs: coverage, freshness categories, and why unparsed reports are included. For a zero-parameter index tool, this is complete.

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 tool has zero parameters, so there is no parameter meaning for the description to add. The empty schema is self-explanatory, and the description appropriately focuses on what the index reports rather than inputs.

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 states a specific resource and scope: an index of USDA AMS daily cash grain bid reports, including covered states, commodities, and freshness. It also distinguishes the tool from cash.bids by explaining that this index is to be called first to learn coverage before fetching bids.

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?

Usage is explicit: 'Call before cash.bids to learn which states are covered and which reports have stopped publishing.' This gives a clear sequencing rule and rationale, and the liveness categories further clarify what the agent will learn before invoking the sibling tool.

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