Skip to main content
Glama

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).

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": {
      "year": "2026",
      "state": "IOWA",
      "commodity": "CORN"
    },
    "name": "nass_crop_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoYear, e.g., "2026". Optional, defaults to current year.
stateNoState name (optional, defaults to national)
_apiKeyYesNASS API key
commodityYesCrop: "CORN", "SOYBEANS", "WHEAT", "COTTON", "SORGHUM"
stat_categoryNoNarrow to "CONDITION" (good/excellent ratings) or "PROGRESS" (planting/harvest %). Optional, omit for both.

Output Schema

NameRequiredDescriptionDefault
dataYesWeekly crop progress and condition reports
countYesNumber of records returned
truncatedYesTrue if results exceed 200 records

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / stat_category / description
      Previous value: -"Narrow to \"CONDITION\" (good/excellent ratings) or \"PROGRESS\" (planting/harvest %). Optional — omit for both."New value: +"Narrow to \"CONDITION\" (good/excellent ratings) or \"PROGRESS\" (planting/harvest %). Optional, omit for both."
    • changedInput schema / properties / year / description
      Previous value: -"Year, e.g., \"2026\". Optional — defaults to current year."New value: +"Year, e.g., \"2026\". Optional, defaults to current year."
  2. Changed1 schema field changed
    • 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"
      +  }
      +]
  3. Changed3 schema fields changed
    • 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"
      +]
  4. Changed1 schema field changed
    • addedInput schema / properties / stat_category
      Added value: +{
      +  "description": "Narrow to \"CONDITION\" (good/excellent ratings) or \"PROGRESS\" (planting/harvest %). Optional — omit for both.",
      +  "type": "string"
      +}
  5. Changed1 schema field changed
    • 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"
      +}
  6. Changed1 schema field changed
    • 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"
      +  }
      +]
  7. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds useful non-annotation behavior: the response contains a condition_summary with the latest national week's ratings plus a combined good_or_excellent_pct, and omitting stat_category returns both categories rather than erroring.

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?

The purpose is front-loaded, followed by the query-type routing and the filter default, with no filler sentences. There is mild duplication with the schema on stat_category behavior, but nothing that costs the reader.

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?

For a five-parameter, filtered-lookup tool with an output schema and full annotation coverage, the definition covers purpose, defaults, and query routing well. Return-value detail is somewhat redundant given the output schema, and pagination/rate-limit behavior is unaddressed, but nothing needed to call 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 coverage is 100%, so every parameter including stat_category's 'omit for both' behavior is already documented structurally. The description largely restates that filter semantics; its only added value is enumerating PROGRESS as planted/emerged/harvested, which is marginal over the schema's 'planting/harvest %'.

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?

The first sentence names the specific resource (weekly USDA crop progress and condition), its grain (by crop and state), and its cadence, which separates it cleanly from production, livestock, and price siblings. It further splits the tool's two output modes (CONDITION vs PROGRESS), so an agent knows exactly what it retrieves.

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?

The description routes the agent by query type: condition questions map to condition_summary, and progress questions require stat_category="PROGRESS". It also states the default when the filter is omitted. It stops short of naming when a different NASS tool (e.g., production) would be the better choice, so it is clear context rather than a full when/when-not guide.

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.