Skip to main content
Glama

x420_geo_flood-zone

Look up the FEMA flood hazard zone at a latitude and longitude, returning zone code, subtype, SFHA flag, and static base flood elevation from the National Flood Hazard Layer.

Instructions

FEMA flood zone at a point: Flood hazard zone(s) intersecting a coordinate from FEMA's National Flood Hazard Layer (layer 28, free, no key): zone code, subtype, SFHA flag, static BFE. Source: FEMA NFHL. Not an official flood zone determination. Not professional, legal, insurance, engineering, medical, financial or tax advice. PAID: $0.05 USDC per call, settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY (real money). Returns: JSON: mapped, in_sfha, zones[{zone, subtype, sfha, static_bfe_ft, dfirm_id}] - the deliverable plus X420's signed receipt and the settlement transaction. Example input: {"lat":"32.7555","lon":"-97.3286"}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "x420_geo_flood-zone"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYeslatitude
lonYeslongitude

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the paid model ($0.05 USDC per call settled on Base from a named env var, real money), the source dataset, and the fact that a signed receipt and settlement transaction come back with the payload. This also explains the non-read-only and non-idempotent hints, since each call costs money and produces a settlement write.

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 payload description is front-loaded and the return shape, cost, and example are each stated once. The legal disclaimer sentence is long and partly redundant with the preceding 'not an official flood zone determination' line, which is the only notable padding.

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 fully specifies the return fields and notes the extra receipt and settlement transaction. Cost, credential source, data source, example call, and caveats are all present, leaving nothing an agent needs missing.

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% and both parameters are simple lat/lon strings, so the schema already carries most of the burden. The description adds a concrete example input showing the string format and decimal precision expected, which is modest but real added value.

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 and scope: FEMA flood hazard zone(s) intersecting a coordinate, from NFHL layer 28. It also enumerates the returned fields (zone code, subtype, SFHA flag, static BFE), which separates it cleanly from siblings like x420_geo_elevation or x420_hail_point-history.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the coordinate-based query and the explicit disclaimer that this is not an official determination, but there is no statement of when to prefer this over related tools (storm, hail, or site-scan siblings) and no when-not guidance. An agent can infer the use case but gets no routing rules.

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