Skip to main content
Glama
Sign In

mu

by mu.micro
OverviewDiscussionsAdmin

Floods hazards

hazards_floods

Flood warnings and alerts in force in England, most severe first, from the Environment Agency. The one hazard here that is a forecast rather than a record — a warning says flooding is expected, which is something you can act on. Optionally near a point. England only, and the answer says so

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": "hazards_floods"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoOptional: only warnings near this point
lonNoOptional: only warnings near this point
severeNoOnly warnings and severe warnings — leave out the be-prepared alerts
within_kmNoOptional: how near, in kilometres, default 30 when a point is given

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations only include a title, so the description must convey behavioral traits. It states the data source, ordering, geographic scope, and the distinction between forecast and record. However, it doesn't mention rate limits, authentication, or what the response structure looks like. The description adds useful context but isn't exhaustive.

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?

Description is relatively concise, but the second sentence is a bit rambling with the 'forecast vs record' nuance. Front-loaded with the key info: 'Flood warnings and alerts in force'. No extraneous marketing. Overall, efficient.

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 simple list tool with no output schema, the description provides key context: data source (Environment Agency), scope (England only), ordering (most severe first), and the semantic nuance of forecast vs record. It doesn't mention pagination, limits, or data format, but for a flood warnings tool, this is reasonable.

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 covers all 4 parameters with descriptions 100%. The description adds context by mentioning 'optionally near a point' and 'most severe first' (ordering), and clarifies that 'severe' filters. However, it doesn't explain the exact interaction (e.g., if within_km only applies when lat/lon given). Since schema already has descriptions, the description's added value is moderate.

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 clearly states the tool provides flood warnings and alerts in force in England, sourced from the Environment Agency, and sorted by severity. It distinguishes itself from sibling tools like hazards_alerts and hazards_quakes by specifying the hazard type (flood) and geographic scope (England only).

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 description indicates the tool is for current flood warnings, mentions the England-only scope, and notes optional proximity filtering. However, it does not explicitly contrast with other hazard tools (e.g., hazards_alerts) to clarify when to prefer this one, though the name and content make it clear.

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

All mu 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