Usda Market News

Ams Report Search

ams_report_search

Read-onlyIdempotent

Find USDA AMS livestock price reports (Livestock Mandatory Price Reporting): national and regional direct slaughter cattle, boxed beef and cow-beef cutouts, hogs and pork, lamb. Filter by words in the title and/or species (cattle, beef, swine, pork, lamb). Returns report_id, report code, title, the sections each report has, and when AMS last published it. Use the report_id with ams_report. Livestock only (produce, grain, hay and cotton: ams_market_report_search); if nothing matches it says so and states what is not covered (it never returns a bare empty list).

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": {
      "query": "boxed beef cutout",
      "species": "beef"
    },
    "name": "ams_report_search"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max reports to return (default 25, max 100).
`query`	No	Words that must all appear in the report title, e.g. "boxed beef cutout" or "weekly direct slaughter".
`species`	No	Restrict to one species / family.

Output Schema

Name	Required	Description	Default
`source`	No
`status`	No
`reports`	No
`coverage`	No
`returned`	No
`data_as_of`	No
`report_family`	No
`total_matches`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so safety is covered; the description adds genuinely new behavior by promising that a non-match never yields a bare empty list but instead states what is not covered. Its summary of return fields (report_id, code, title, sections, last published) is somewhat redundant given a full output schema exists, which keeps this from a 5.

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-loaded with the resource scope, then routing, then return shape — every sentence carries signal. It is slightly dense with enumerations (seven commodity types, five species) that partly duplicate the enum in the schema, costing some tightness.

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?

Complete for a three-optional-parameter, read-only search: annotations cover the safety profile, an output schema covers return values, and the description covers domain scope, species/commodity boundaries, the empty-result behavior, and the intended follow-up call. Nothing an agent needs to invoke it correctly is missing.

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 100%, so query, species (with its enum) and limit are already fully documented. The description only restates that filtering is by title words and/or species; it adds no syntax, matching semantics (e.g. case sensitivity, stemming) or limit behavior beyond the schema, so the baseline 3 applies.

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 (Find) and a precisely scoped resource (USDA AMS Livestock Mandatory Price Reporting reports), enumerating the covered commodities (direct slaughter cattle, boxed beef and cow-beef cutouts, hogs/pork, lamb). It also names the sibling it is not (ams_market_report_search) and what that sibling covers, so the agent can route without opening schemas.

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?

Gives explicit filtering instructions (title words and/or species) and explicit exclusion guidance: 'Livestock only (produce, grain, hay and cotton: ams_market_report_search).' It also prescribes the follow-up step — use the returned report_id with ams_report — which tells the agent how this tool fits into a chain rather than standing alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Usda Market News tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.