Crosby, TX Weather

River & bayou levels

get_river_levels

Read-onlyIdempotent

Current water levels and NWS flood stages for the rivers and bayous that flood Crosby, TX and northeast Harris County (Cedar Bayou, San Jacinto River, Luce Bayou, and more). Each gauge reports its stage, flow, flood category, and thresholds.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`gauges`	Yes
`source`	No
`updated`	No	ISO 8601 timestamp of the last data refresh.
`location`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 7, 2026
- addedOutput schema / properties / gauges / items / properties / flow / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / gauges / items / properties / flow / type
```
Removed value: -[
-  "number",
-  "null"
-]
```
- addedOutput schema / properties / gauges / items / properties / stage / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / gauges / items / properties / stage / type
```
Removed value: -[
-  "number",
-  "null"
-]
```
- addedOutput schema / properties / updated / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / updated / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

Changed1 schema field changedJul 14, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "gauges": {
+      "items": {
+        "properties": {
+          "category": {
+            "description": "no_flooding/action/minor/moderate/major, or not_defined where NWS defines no flood stages.",
+            "type": "string"
+          },
+          "flow": {
+            "description": "Observed discharge in cfs.",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "officialUrl": {
+            "type": "string"
+          },
+          "stage": {
+            "description": "Observed gauge height in ft.",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "thresholds": {
+            "description": "NWS flood-stage thresholds in ft, keyed action/minor/moderate/major.",
+            "type": "object"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "location": {
+      "type": "string"
+    },
+    "source": {
+      "type": "string"
+    },
+    "updated": {
+      "description": "ISO 8601 timestamp of the last data refresh.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "gauges"
+  ],
+  "type": "object"
+}

First observedJul 13, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and closed-world behavior, so the safety profile is covered. The description adds that values are current and sourced as NWS flood stages and lists gauge fields, but it omits refresh cadence, latency, and gauge coverage limits. With an output schema documenting return fields, this is a moderate rather than rich behavioral disclosure.

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?

Two sentences, front-loaded with purpose and scope; examples add specificity without bloat. The final field list is slightly return-oriented, but the whole definition remains tight and easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, read-only tool with a full output schema and rich annotations, the description gives scope, source, and data categories. It does not name when to prefer get_alerts or get_current_conditions and lacks freshness details, so it is strong but not exhaustive.

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?

There are zero input parameters, so the baseline is 4. The description has no parameter semantics to add and correctly does not invent any.

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 resource (current water levels and NWS flood stages), a precise geographic scope, named waterways, and per-gauge fields. No sibling tool covers river/bayou gauges, so it is readily distinguishable from get_current_conditions, get_alerts, get_forecast, and get_radar.

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?

Establishes clear context—flood-prone rivers and bayous around Crosby, TX and northeast Harris County—and implies use for local flood-stage monitoring. It does not explicitly say when to prefer get_alerts for warnings or get_forecast for future river forecasts, so it lacks exclusions and named alternatives.

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

All Crosby, TX Weather tools Inspect

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.