Skip to main content
Glama

NWS warning history for Crosby

get_warning_history
Read-onlyIdempotent

How many National Weather Service warnings, watches and advisories have covered Crosby, TX, by type and year, computed from the site's record: tornado, severe thunderstorm, flash flood and flood warnings whose polygon contained Crosby (counted from 2007-10-01, when polygons became the official warned area), products for forecast zone TXZ213 (tropical, winter, heat, fire weather, fog; the zone has been redrawn), and Harris County watches. Includes the date of every tornado warning. For active alerts use get_alerts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_warning_history"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
pageNo
zoneNo
notesNo
byYearNo
sourceNo
totalsYesPolygon warnings containing Crosby, keyed tornado/severeThunderstorm/flashFlood/floodWarning/floodAdvisory.
zoneProductsNo
countyWatchesNo
tornadoWarningsNo
polygonsCountedFromNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive/closed-world, so safety is covered. The description goes further with data-provenance caveats an agent needs to interpret results honestly: counting starts 2007-10-01 when polygons became the official warned area, the forecast zone has been redrawn, and every tornado warning date is included.

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 lead is front-loaded with the actual question the tool answers, and the trailing guidance sentence earns its place. The middle is a single dense run-on clause listing hazard types, which is information-bearing but harder to scan than a short enumerated list.

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?

An output schema exists, so return shape need not be explained. The description instead supplies the coverage boundaries that determine what the numbers mean: polygon era start date, zone-based products, county watches, and the per-type/per-year breakdown. Nothing an agent needs to invoke or interpret it correctly is missing.

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?

The tool takes no parameters, so there is no per-argument meaning to add and the schema already forecloses extras via additionalProperties:false. Baseline for a zero-parameter tool applies; the description correctly adds no spurious parameter claims.

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 and resource: counting NWS warnings, watches and advisories covering Crosby, TX by type and year. It enumerates the hazard categories covered and the geographic basis (polygon containment, forecast zone TXZ213, Harris County watches), which lets an agent distinguish it from get_alerts and get_flood_history without opening either schema.

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 closing sentence gives an explicit alternative: 'For active alerts use get_alerts,' which cleanly separates historical aggregation from current conditions. It does not spell out when-not cases beyond that (e.g., how it differs from get_flood_history), so it falls 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.