Skip to main content
Glama
Sign In
xippios-mcp

xippios-mcp

by xippios
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

usda_nass_get_crop_progress

Read-onlyIdempotent

Retrieves weekly USDA NASS crop progress percentages—planted, emerged, silking, harvested—for a commodity and year, filtered by state and stage. Use it to track planting and harvest pace.

Instructions

Weekly crop progress: the percentage planted, emerged, silking, harvested and so on.

One row per week and stage, from the NASS Crop Progress survey (statisticcat_desc PROGRESS, freq_desc WEEKLY), sorted by week. Stages differ by crop; unit_desc names each one and value is the percentage.

Args: commodity: Upstream commodity_desc, e.g. "CORN", "SOYBEANS", "WINTER WHEAT", "COTTON"; list_param_values("commodity_desc") lists them. year: Crop year, e.g. 2024. state: Two-letter state code for the state series; None returns the national US TOTAL series. stage: A single stage, e.g. ProgressStage.PCT_PLANTED, ProgressStage.PCT_SILKING, ProgressStage.PCT_HARVESTED; the enum lists every stage any crop uses, and None returns every stage of this crop.

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>",
      "year": "<year>"
    },
    "name": "usda_nass_get_crop_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
stageNo
stateNo
commodityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely useful behavior: the underlying survey filter, one-row-per-week-and-stage granularity, and week-based sorting. It stops short of discussing coverage gaps (e.g. not every crop reports every stage) or release timing.

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 one-sentence summary and row shape before the Args block, and no sentence is filler. The backticked parentheticals and enum-member examples add some visual noise without adding meaning.

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?

There is no output schema, yet the description fully specifies the return shape: one row per week and stage, sorted by week, with unit_desc naming the stage and value holding the percentage. Combined with complete parameter semantics, an agent has everything needed to call and interpret this tool.

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 0%, so the description carries the full burden and mostly delivers: commodity examples with a lookup pointer, year as crop year, state as a two-letter code with None meaning national, and stage with None meaning all stages. The one weakness is that stage examples are written as Python enum members (ProgressStage.PCT_PLANTED) while the schema enum values are plain strings like 'PCT PLANTED', which could cause a malformed argument.

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 and resource (weekly crop progress percentages) and pins the exact source series (statisticcat_desc PROGRESS, freq_desc WEEKLY). The distinction from the sibling usda_nass_get_crop_condition is implicit but clear: this returns stage percentages, not condition ratings.

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 usage context: which commodities to pass, that state=None yields the national US TOTAL series, and that stage=None returns every stage for the crop. It also routes the agent to usda_nass_list_param_values for valid commodity values. It does not explicitly name a competing sibling or state when not to use this tool.

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

Deploy Server

Other Tools