Skip to main content
Glama

Nfhl Query

nfhl_query
Read-onlyIdempotent

Query any layer of the FEMA National Flood Hazard Layer with an ArcGIS WHERE clause and optional bounding box, flood hazard zones, base flood elevations, floodways, LOMRs and LOMAs, FIRM panels with their effective dates, levees, cross-sections, political jurisdictions. Use for area questions ("every floodway polygon in this county", "LOMRs issued on this DFIRM"). Layer ids come from nfhl_layers.

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": {
      "limit": 5,
      "where": "DFIRM_ID='48201C' AND FLD_ZONE='AE'",
      "layer_id": 28,
      "out_fields": "FLD_ZONE,ZONE_SUBTY,SFHA_TF,STATIC_BFE,DFIRM_ID"
    },
    "name": "nfhl_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
bboxNoOptional "xmin,ymin,xmax,ymax" WGS84 envelope to restrict the query (longitude first)
limitNoMax rows, 1-500 (default 50)
whereNoArcGIS WHERE clause, default "1=1". Id fields are strings: DFIRM_ID='48201C'.
offsetNoRow offset for paging
layer_idYesNFHL layer id, 28 is Flood Hazard Zones, 16 Base Flood Elevations, 1 LOMRs, 3 FIRM Panels
order_byNoComma-separated order-by fields
out_fieldsNoComma-separated field names, or "*" for all (default "*")
return_geometryNoInclude geometry. Default false, flood polygons are very large.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / layer_id / description
      Previous value: -"NFHL layer id — 28 is Flood Hazard Zones, 16 Base Flood Elevations, 1 LOMRs, 3 FIRM Panels"New value: +"NFHL layer id, 28 is Flood Hazard Zones, 16 Base Flood Elevations, 1 LOMRs, 3 FIRM Panels"
    • changedInput schema / properties / return_geometry / description
      Previous value: -"Include geometry. Default false — flood polygons are very large."New value: +"Include geometry. Default false, flood polygons are very large."
  2. First observed

TDQS

A3.9/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 openWorldHint, so the safety profile is covered. The description adds no behavior beyond that: nothing about the remote ArcGIS service's error modes, rate limits, or result paging behavior. It is consistent with the annotations but thin on added context.

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?

The verb and resource are front-loaded, and the second sentence is a compact routing/usage cue. The long enumeration of data domains is list-like but each item earns its place by telling the agent what can be queried. No filler or repetition.

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 an 8-parameter read tool with 100% schema coverage and full annotations, the description covers purpose, layer-id sourcing and example intents. The main residual gap is that with no output schema, the description never says what a result row looks like (attributes vs. geometry) or how paging interacts with limit. That is a modest but real omission.

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%, so the schema already documents bbox, where, limit, offset, layer_id, order_by, out_fields and return_geometry, including the layer id examples 28/16/1/3. The description contributes semantic framing by naming what those layer types contain and by showing a DFIRM-scoped query intent, but it does not add syntax or format detail beyond the schema. Baseline 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?

Opens with a specific verb and resource: "Query any layer of the FEMA National Flood Hazard Layer with an ArcGIS WHERE clause and optional bounding box." It then enumerates the concrete content domains (zones, BFEs, floodways, LOMRs/LOMAs, FIRM panels, levees, cross-sections, jurisdictions) and points to nfhl_layers for layer ids, which separates it from the point-lookup sibling.

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?

Explicit use-case framing is given: "Use for area questions" with two concrete example questions tied to floodways and LOMRs. It also states the prerequisite workflow (layer ids come from nfhl_layers). It stops short of stating when NOT to use it, e.g. that single-point lookups should go to nfhl_flood_zone_at_point.

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.