Skip to main content
Glama

Us Drought National

us_drought_national
Read-onlyIdempotent

Weekly U.S. Drought Monitor drought-severity statistics for the nation: percent of area or percent of population in categories None, D0 (abnormally dry) through D4 (exceptional drought). Categories are cumulative (D1+ means D1 through D4 combined, i.e. 'at least moderate drought'). Covers the contiguous 48 states (conus), the contiguous states plus Alaska/Hawaii/Puerto Rico (total), or both at once (us). Published weekly, map valid every Tuesday, released the following Thursday. Omit dates for the latest available map.

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": {
      "area": "conus"
    },
    "name": "us_drought_national"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoconus = contiguous 48 states only. total = contiguous states plus Alaska, Hawaii, and Puerto Rico. us = both rows at once. Default conus.
measureNo'area' = percent of land area in each category (default). 'population' = percent of the area's population in each category.
end_dateNoLatest map date, YYYY-MM-DD or M/D/YYYY. Omit for the latest single map.
start_dateNoEarliest map date, YYYY-MM-DD or M/D/YYYY. Omit for the latest single map.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, open-world behavior, and the description adds genuinely new behavioral context: weekly cadence, a Tuesday map validity date, a Thursday release lag, and the cumulative semantics of the D-categories. The freshness/latency disclosure is exactly what an agent needs to judge whether the data is current, which no structured field provides.

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 resource and severity categories, then coverage, then cadence and the date tip — a sensible information order with no filler. The closing sentence on omitting dates slightly repeats the schema's 'Omit for the latest single map', a minor redundancy, but the rest is dense and purposeful.

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 carries the burden of describing returns, and it does: percentages of area or population across None and D0-D4 with cumulative-category meaning spelled out. Combined with publication cadence and coverage definitions, an agent has everything needed to call it and interpret results 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 coverage is 100%, so the schema already defines area, measure, and both date parameters, including their enum values. The description's notes on conus/total/us and on omitting dates largely restate the schema, and the useful clarification about cumulative categories applies to the result values rather than the inputs, so the baseline 3 holds.

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?

States a specific verb and resource: weekly U.S. Drought Monitor drought-severity statistics, with the scope pinned down as national (conus/total/us). The phrase 'for the nation' signals it is the national aggregate rather than county or state data, though it never names the sibling tools that cover those scopes, leaving the routing differentiation implicit.

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?

Gives clear operational guidance on dates ('Omit dates for the latest available map') and defines the area/measure dimensions, but says nothing about when to prefer this over us_drought_county or us_drought_state. Usage is implied by the 'national' framing rather than stated as an explicit when-to-use rule.

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.