Skip to main content
Glama

LiveDataLink

by io.github.blackboxfoundry
OverviewDiscussionsAdmin

usda_nass_compare_crop_years

Read-onlyIdempotent

Compare 2–7 requested crop years across every hosted area, yield, and production metric for one USDA NASS crop/class. Returns each component value with its own unit and source release file, missing-year evidence, provenance, and caveats. Use this for 'compare 2019 and 2025 corn', '2020 vs 2025 soybean acres and yield', or 'compare winter wheat output across these years'. Final national annual summaries only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cropYesCrop name or supported alias: corn, soybeans, cotton, wheat, winter wheat, durum wheat, or spring wheat.
yearsYesTwo to seven distinct crop years.
crop_classNoOptional class. Required for bare 'wheat': winter, durum, or spring (excluding durum).
response_formatNoHuman-readable markdown or machine-readable JSON. Default markdown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / properties / crop / maxLength
      Added value: +80
    • addedInput schema / properties / crop / minLength
      Added value: +1
    • addedInput schema / properties / crop_class / maxLength
      Added value: +80
    • addedInput schema / properties / crop_class / minLength
      Added value: +1
    • addedInput schema / properties / years / items / maximum
      Added value: +2100
    • addedInput schema / properties / years / items / minimum
      Added value: +1900
    • changedInput schema / properties / years / items / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / years / maxItems
      Added value: +7
    • addedInput schema / properties / years / minItems
      Added value: +2
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld). The description adds useful behavioral context by disclosing return components (units, source release file, missing-year evidence, provenance, caveats) and a scope boundary (national annual summaries only).

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?

The description is front-loaded with the core operation, then adds return information and usage examples. Every sentence earns its place without redundancy or excessive length.

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?

With no output schema, the description adequately explains what is returned and includes provenance and missing-year caveats. The schema already covers parameters at 100%, and annotations cover safety, so the agent has enough to invoke the tool correctly.

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 the schema already documents all four parameters including crop aliases, year limits, crop_class handling, and response_format. The description reinforces the 2–7 year range and single crop/class constraint but adds no parameter syntax or format details beyond the schema, so the baseline 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?

The description states a specific verb-resource pair (compare crop years) and constrains it to one USDA NASS crop/class and final national annual summaries. It clearly distinguishes a multi-year comparison tool from sibling search/history/trend tools by defining the comparison scope.

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?

It gives concrete usage examples ('compare 2019 and 2025 corn', '2020 vs 2025 soybean acres and yield') and a scope limitation ('Final national annual summaries only'). It does not explicitly name alternative sibling tools or state when not to use it, so it stops short of full routing guidance.

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

All LiveDataLink toolsInspect
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.

Resources