Skip to main content
Glama

Flood history of Crosby's river gauges

get_flood_history
Read-onlyIdempotent

The flood record for the river gauges near Crosby, TX that have one (Cedar Bayou near Crosby, the San Jacinto River near Sheldon and at Lake Houston, the East Fork San Jacinto near New Caney): each gauge's highest historic crests as NOAA publishes them, measured against TODAY's NWS flood stages (stages may have differed when a crest happened), how many crests and river flood warnings the record holds, and a link to the full page. Crests NOAA marks as on an older gauge datum are counted but never compared. For current levels use get_river_levels.

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_flood_history"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
noteNo
gaugesYes
sourceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedOutput schema / properties / gauges / items / properties / highestCrests / items / properties / noaaCode / description
      Previous value: -"NOAA's one-letter code, as published; NOAA does not define it."New value: +"The letter NWPS publishes for that status (P, O, R)."
    • addedOutput schema / properties / gauges / items / properties / highestCrests / items / properties / noaaFlowCfs
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Crest flow as NOAA publishes it; null when none, or on gauges where NOAA's figure is not a measured flow."
      +}
    • addedOutput schema / properties / gauges / items / properties / highestCrests / items / properties / status
      Added value: +{
      +  "description": "NWS crest status: Preliminary, Official or Record (— when none).",
      +  "type": "string"
      +}
    • addedOutput schema / properties / gauges / items / properties / highestCrests / items / properties / usgsFlowCfs
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "USGS's annual peak flow, when that year's peak falls on the crest's date."
      +}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare this a safe, idempotent, closed-world read, so the remaining burden is output semantics — and the description covers them well: crests are compared against today's NWS flood stages (with the caveat that stages may have differed historically), crests on older gauges' datums are counted but never compared, and a source link is returned. These are non-obvious interpretive rules an agent could not infer from the annotations or an empty input schema.

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?

Content is front-loaded with the resource and the coverage, then the return semantics, then the sibling pointer. The long mid-sentence parenthetical listing four gauges is dense but carries genuine scoping information; only minor trimming would be possible without losing substance.

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 an output schema present, the description needn't document return shapes, and it still explains the interpretive rules (datum handling, present-day stage comparison) that the output schema cannot convey. Nothing an agent needs in order to call this no-argument tool 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 zero parameters, so there is nothing for the description to disambiguate and the schema is inherently complete. The description's gauge enumeration implicitly scopes the fixed coverage, which is mild value-add beyond an empty object schema.

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 — 'flood record for the river gauges near Crosby, TX' — and enumerates the exact gauges covered (Cedar Bayou, San Jacinto near Sheldon, Lake Houston, East Fork near New Caney). It also differentiates itself from get_river_levels, so an agent can pick between the historical and current tools without opening a 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 final sentence gives an explicit routing rule: 'For current levels use get_river_levels,' which is exactly the ambiguity an agent faces here. It lacks any when-not guidance for the other plausible alternative, get_warning_history, even though the description mentions warnings are counted in this record.

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.