Nass

Nass Crop Production

nass_crop_production

Read-onlyIdempotent

Get US crop yields, production totals, and planted/harvested acreage by crop, state, and year. Quick access to major crop survey data.

Input Schema

TableJSON Schema

Name	Required	Description
`year`	No	Year or range, e.g., "2024" or "2020:2025" (optional)
`state`	No	State name, e.g., "IOWA" (optional, defaults to national)
`_apiKey`	Yes	NASS API key
`commodity`	Yes	Crop name: "CORN", "SOYBEANS", "WHEAT", "COTTON", "RICE", "SORGHUM", "BARLEY", "OATS"
`stat_category`	No	Statistic: "PRODUCTION", "YIELD", "AREA PLANTED", "AREA HARVESTED" (default: "PRODUCTION")

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Crop production and yield data
`count`	Yes	Number of records returned
`truncated`	Yes	True if results exceed 200 records

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of records returned",
+      "type": "integer"
+    },
+    "data": {
+      "description": "Crop production and yield data",
+      "items": {
+        "properties": {
+          "agg_level": {
+            "description": "Aggregation level",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "commodity": {
+            "description": "Crop name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "county": {
+            "description": "County name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "description": {
+            "description": "Statistic description",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "frequency": {
+            "description": "Frequency",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "period": {
+            "description": "Reference period",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "stat_category": {
+            "description": "Statistic (PRODUCTION, YIELD, AREA PLANTED, AREA HARVESTED)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "state": {
+            "description": "State name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "unit": {
+            "description": "Unit of measurement",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "value": {
+            "description": "Production, yield, or acreage value",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "year": {
+            "description": "Year of the record",
+            "type": [
+              "integer",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "truncated": {
+      "description": "True if results exceed 200 records",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "count",
+    "data",
+    "truncated"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "_apiKey": "your-nass-api-key",
+    "commodity": "CORN",
+    "stat_category": "PRODUCTION",
+    "state": "IOWA"
+  },
+  {
+    "_apiKey": "your-nass-api-key",
+    "commodity": "WHEAT",
+    "stat_category": "YIELD",
+    "year": "2020:2025"
+  }
+]

First observedApr 22, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive. Description adds that it's 'quick access to major crop survey data', but doesn't detail return size, pagination, or rate limits. No contradiction.

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?

Two concise sentences, front-loaded with the action, no unnecessary words. Efficiently communicates purpose.

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?

Adequate given existence of output schema and clear schema examples. Could mention default behavior (national/year) but not essential. Complete enough for agent invocation.

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?

All 5 parameters have full schema descriptions (100% coverage). The description adds no additional meaning beyond the schema, so baseline score 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?

Description clearly states verb 'Get' and specific resources: crop yields, production totals, planted/harvested acreage. Distinct from sibling tools like nass_crop_progress (progress) and nass_prices (prices).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use vs alternatives like nass_query or nass_crop_progress. Usage is implied by name and description but not clarified.

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

All Nass 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.