Skip to main content
Glama

Ams Report

ams_report
Read-onlyIdempotent

Read dated rows from one USDA AMS livestock price report (Livestock Mandatory Price Reporting). Every response states the report family, report title, market type and office, and each row keeps its own basis fields (class, selling basis, grade, weight range) plus price low / high / weighted-average as separate fields: ranges are never collapsed and nothing is averaged here. Pick a section (see sections in ams_report_search; prices are usually in "Detail", not "Summary"). With no date it returns the most recent report date. If AMS has no rows for the requested date or section (not published yet, holiday, wrong section) the result is status "no_rows_for_request" with the report's last published date, not an empty array. Dates are ISO (2026-10-22).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "2026-10-19",
      "limit": 20,
      "section": "Detail",
      "report_id": 2477
    },
    "name": "ams_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoOne report date, ISO YYYY-MM-DD.
limitNoMax rows (default 100, max 500). Newest first.
sectionNoSection name, case-insensitive (default "Summary"), e.g. "Detail".
end_dateNoRange end, ISO.
report_idYesReport id from ams_report_search, e.g. 2466 (5 Area Daily Weighted Average Direct Slaughter Cattle).
start_dateNoRange start, ISO (use with end_date).

Output Schema

NameRequiredDescriptionDefault
rowsNo
reportNo
sourceNo
statusNo
sectionNo
completeNo
returnedNo
report_idNo
requestedNo
row_countNo
unit_noteNo
data_as_ofNo
report_familyNo
sections_availableNo
report_last_publishedNo
report_dates_in_resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds behavior annotations cannot: the non-obvious "no_rows_for_request" status with the report's last published date instead of an empty array, and the guarantee that ranges are never collapsed and nothing is averaged. Missing only secondary traits like pagination order confirmation or rate limits (limit ordering is in the schema).

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?

Front-loads the resource and the row shape before the operational caveats, and most sentences carry distinct information. The trailing ISO-date reminder largely duplicates the schema's date description, a small redundancy in an otherwise dense, well-ordered paragraph.

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?

An output schema exists so return values need not be spelled out, yet the description still covers the one surprising response case and the row-fidelity guarantees. What remains incomplete is range-query behavior for start_date/end_date and how it interacts with a single date.

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, but the description adds real meaning beyond the schema: omitting the date yields the most recent report date, and section choice materially affects whether prices appear. The start_date/end_date pair is left unexplained, so it does not fully compensate for that one semantic hole.

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: read dated rows from one USDA AMS livestock price report, with the domain named explicitly (Livestock Mandatory Price Reporting). It also distinguishes itself from ams_report_search by positioning that sibling as the discovery step and describes the exact row shape returned.

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 routes the agent to ams_report_search for section names and warns that prices are usually in "Detail", not the default "Summary" — actionable selection guidance. It also states the no-date default. It does not explain when to use the date range parameters (start_date/end_date) instead of a single date, which is a real gap for a 6-param 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.