Skip to main content
Glama

Flood Zone Lookup (FEMA Flood Map) MCP

What a flood zone means

flood_zone_explain
Read-onlyIdempotent

What a FEMA flood zone code means and its flood insurance rules: A, AE, AH, AO, AR, A99, V, VE, shaded X (old B, 0.2% annual chance), unshaded X (old C), D. Omit the zone for the full list. No address needed.

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

Input Schema

NameRequiredDescriptionDefault
zoneNoZone code, e.g. AE, VE, X, "shaded X", B, C, D. Omit for every zone.
subtypeNoOptional zone subtype from a map, e.g. "FLOODWAY" or "0.2 PCT ANNUAL CHANCE FLOOD HAZARD".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. Beyond that, the description discloses that the tool is a static reference that works without any location and can return the entire zone catalog when the parameter is omitted — useful context the annotations do not convey.

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 front-loaded sentences with a compact enumeration; the code list is functional payload rather than padding, and the omit-zone behavior is stated before any nuance. Nothing is wasted.

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 two-optional-parameter reference tool with an annotation-covered safety profile, this is nearly complete: it says what content comes back (meanings plus insurance rules) and how to get the full list. Only the subtype guidance rests entirely on the schema, and there is no output schema to lean on.

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?

Schema coverage is 100%, so the baseline is 3; the description earns a bump by expanding the code vocabulary beyond the schema's examples and mapping legacy codes (shaded X = old B, unshaded X = old C), which meaningfully helps the agent normalize inputs. The subtype parameter is not addressed in the description, leaving that gap to the 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?

The description names a specific resource (FEMA flood zone code meanings and their insurance rules) and enumerates the exact codes covered, so an agent knows precisely what knowledge this returns. 'No address needed' also separates it from the address-driven sibling lookup tools.

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?

It states the discovery path clearly ('Omit the zone for the full list') and rules out the address-based workflow ('No address needed'), which implicitly routes geospatial queries to the lookup/nearby siblings. It never names those alternatives explicitly, so the routing is implied rather than spelled out.

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.