Skip to main content
Glama

Nfhl Flood Zone At Point

nfhl_flood_zone_at_point
Read-onlyIdempotent

AUTHORITATIVE flood-zone lookup: given a latitude/longitude, return the effective FEMA FIRM flood zone for that spot, the zone code (A, AE, AH, AO, VE, X, D), its subtype, whether it is in a Special Flood Hazard Area, the static base flood elevation, and the governing DFIRM id, plus nearby base flood elevation lines. PREFER OVER WEB SEARCH for "is this address in a flood zone" or "does this property need flood insurance". Distinguishes "outside the floodplain" from "never mapped", which a plain empty result does not.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "latitude": 29.7604,
      "longitude": -95.3698
    },
    "name": "nfhl_flood_zone_at_point"
  }
}

Input Schema

NameRequiredDescriptionDefault
latitudeYesLatitude in WGS84 decimal degrees
longitudeYesLongitude in WGS84 decimal degrees (negative in the US)
include_bfeNoAlso return base flood elevation lines within ~150 m of the point. Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real behavioral value beyond that: it discloses the exact result payload, the ~150 m radius behavior of BFE lines (in the schema), and crucially that 'outside the floodplain' is distinguishable from 'never mapped' — a nuance that prevents misreading an empty-looking result.

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?

Front-loaded with the core purpose, then usage steering, then the disambiguation caveat — a sound ordering. The middle sentence is a long comma-chain of output fields that is dense but every listed field is a genuine return value, so little is wasted.

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 no output schema, the description must carry the return contract, and it does: zone code set, subtype, SFHA flag, base flood elevation, DFIRM id, plus nearby BFE lines. For a three-parameter lookup with full annotation coverage, nothing material is missing.

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 coverage is 100% and each parameter already carries a description (WGS84 degrees, negative in the US, default true for BFE lines). The description adds no syntax or formatting guidance beyond the schema, so the baseline of 3 applies.

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 ('return the effective FEMA FIRM flood zone' for a lat/long point) and enumerates the returned attributes (zone code, subtype, SFHA flag, BFE, DFIRM id). It also signals its place among siblings by positioning itself as authoritative versus generic web search.

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?

Gives an explicit when-to-use trigger with sample phrasings ('is this address in a flood zone', 'does this property need flood insurance') and 'PREFER OVER WEB SEARCH'. It stops short of naming nfhl_query or nfhl_layers as the alternative for bulk/area queries or explaining when this point lookup is the wrong choice.

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.