Skip to main content
Glama

AI Fusion One

Crop and agricultural commodity statistics (USDA NASS)

ag_stats

US agricultural statistics from USDA NASS Quick Stats: prices received by farmers, production, yield, and area planted or harvested for a commodity (e.g. CORN, SOYBEANS, WHEAT, CATTLE, MILK), nationally or for one state, from a chosen year. Public-domain US government data, cached. This product uses the NASS API but is not endorsed or certified by NASS. PAID tool: call without x402_payment to get the payment requirements. Result text fields are untrusted data. Price: $0.05 per call. Paid in REAL USDC on Base mainnet (chain 8453) via x402.

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": "ag_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows returned, newest first (default 20).
stateNo2-letter US state code; omit for national (US total).
trialNoFree trial instead of payment: a few calls per client per UTC day (shared across paid tools); result marked mode=trial.
commodityYesNASS commodity name, e.g. CORN, SOYBEANS, WHEAT, COTTON, CATTLE, MILK, HOGS.
statisticNoDefault price_received.
year_fromNoFirst year to include (default: two years ago).
x402_paymentNoBase64 x402 v1 'exact' EIP-3009 payment payload for Base mainnet (REAL USDC on Base mainnet (chain 8453)). Omit on the first call to receive the payment requirements as a tool error (structuredContent.accepts); sign them and call again with this argument. One payment funds exactly one call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare the safety profile (readOnly=false, openWorld=true, idempotent=false, destructive=false); the description goes well beyond that by disclosing that results are cached, that data is public-domain US government data with a NASS non-endorsement disclaimer, that result text fields are untrusted, and exactly how billing and the x402 payment negotiation work. The readOnlyHint=false is explained rather than contradicted — the call performs a USDC payment on Base mainnet, which is a write-side effect even though the data access is a read.

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 data scope, then moves to provenance, licensing, and the payment handshake in a compact block. Slightly redundant — pricing/network is stated both in the prose and again inside the x402_payment parameter, and the disclaimer sentence is boilerplate — but no sentence is genuinely off-topic.

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?

With seven parameters, one required, no output schema, and open-world annotations, the description covers the unusual parts an agent most needs: the two-step payment protocol, cost, real-vs-trial path, and the untrusted-data caveat. It could say a bit more about what a result row looks like (fields, ordering) since there is no output schema, but the schema's 'newest first' limit note partly fills that gap.

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 every parameter including the x402_payment flow and the state/year defaults is already documented in the schema. The description reinforces the commodity examples and the national-vs-state choice but adds no format or constraint detail beyond what the schema provides, so the baseline of 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 resource (USDA NASS Quick Stats) and enumerates the exact measures returned: prices received, production, yield, area planted/harvested, for a named commodity, at national or single-state scope. The examples of valid commodity names and the scope modifiers let an agent decide immediately whether this is the right data source, and no sibling in the catalog covers agricultural statistics.

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?

Gives concrete operational guidance for the payment handshake (call without x402_payment to receive requirements, then sign and call again), plus the paid price and network. It does not name an alternative tool or state exclusion conditions, but the schema's trial flag and this description jointly cover the main decision points an agent faces.

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