Nass

Nass Crop Progress

nass_crop_progress

Read-onlyIdempotent

Weekly USDA crop progress + condition by crop and state. For CONDITION queries ("what % of corn is good or excellent", "crop condition this week") the response includes a condition_summary with the latest national week's ratings AND the standard combined good_or_excellent_pct. For PROGRESS use stat_category="PROGRESS" (planted/emerged/harvested %). Pass stat_category to narrow (otherwise both are returned).

Input Schema

Name	Required	Description
`year`	No	Year, e.g., "2026". Optional — defaults to current year.
`state`	No	State name (optional, defaults to national)
`_apiKey`	Yes	NASS API key
`commodity`	Yes	Crop: "CORN", "SOYBEANS", "WHEAT", "COTTON", "SORGHUM"
`stat_category`	No	Narrow to "CONDITION" (good/excellent ratings) or "PROGRESS" (planting/harvest %). Optional — omit for both.

Output Schema

Name	Required	Description
`data`	Yes	Weekly crop progress and condition reports
`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 changedSep 27, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "_apiKey": "your-nass-api-key",
-    "commodity": "CORN",
-    "state": "IOWA",
-    "year": "2026"
-  },
-  {
-    "_apiKey": "your-nass-api-key",
-    "commodity": "SOYBEANS",
-    "year": "2026"
-  }
-]New value: +[
+  {
+    "commodity": "CORN",
+    "state": "IOWA",
+    "year": "2026"
+  },
+  {
+    "commodity": "SOYBEANS",
+    "year": "2026"
+  }
+]

Changed3 schema fields changedAug 5, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "_apiKey": "your-nass-api-key",
-    "commodity": "CORN",
-    "state": "IOWA",
-    "year": "2024"
-  },
-  {
-    "_apiKey": "your-nass-api-key",
-    "commodity": "SOYBEANS",
-    "year": "2024"
-  }
-]New value: +[
+  {
+    "_apiKey": "your-nass-api-key",
+    "commodity": "CORN",
+    "state": "IOWA",
+    "year": "2026"
+  },
+  {
+    "_apiKey": "your-nass-api-key",
+    "commodity": "SOYBEANS",
+    "year": "2026"
+  }
+]

changedInput schema / properties / year / description

Previous value: -"Year, e.g., \"2024\" (required for progress data)"New value: +"Year, e.g., \"2026\". Optional — defaults to current year."

changedInput schema / required

Previous value: -[
-  "_apiKey",
-  "commodity",
-  "year"
-]New value: +[
+  "_apiKey",
+  "commodity"
+]

Changed1 schema field changedJul 13, 2026

addedInput schema / properties / stat_category

Added value: +{
+  "description": "Narrow to \"CONDITION\" (good/excellent ratings) or \"PROGRESS\" (planting/harvest %). Optional — omit for both.",
+  "type": "string"
+}

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of records returned",
+      "type": "integer"
+    },
+    "data": {
+      "description": "Weekly crop progress and condition reports",
+      "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": "Progress metric description",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "frequency": {
+            "description": "Always WEEKLY",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "period": {
+            "description": "Week reference period",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "stat_category": {
+            "description": "Progress stage (e.g., PLANTED, EMERGED, CONDITION)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "state": {
+            "description": "State name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "unit": {
+            "description": "Unit (e.g., PCT, rating category)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "value": {
+            "description": "Progress percentage or condition rating",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "year": {
+            "description": "Year",
+            "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",
+    "state": "IOWA",
+    "year": "2024"
+  },
+  {
+    "_apiKey": "your-nass-api-key",
+    "commodity": "SOYBEANS",
+    "year": "2024"
+  }
+]

First observedApr 22, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive. The description adds that both progress and condition are returned by default, and that condition queries include condition_summary and good_or_excellent_pct, which is valuable behavioral context.

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?

Three sentences, front-loaded with purpose, and organized logically from overview to specifics. It's concise but covers essential details without unnecessary verbosity.

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?

Given an output schema exists, the description doesn't need to detail return values. It explains the two modes, the default behavior, and how to narrow results. This is sufficient for an agent to call it correctly.

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 baseline is 3. The description adds meaning to stat_category by explaining the two values and their effect on the response, plus the default behavior when omitted, going beyond the schema's brief description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it provides weekly USDA crop progress and condition by crop and state, with examples. It distinguishes itself from siblings by focusing on progress/condition, though it doesn't explicitly name alternatives like nass_crop_production.

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?

Provides clear guidance on using stat_category for condition vs progress and explains that omitting it returns both. However, it doesn't compare to sibling tools like nass_query or nass_crop_production, so cross-tool usage is implied rather than explicit.

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.