Skip to main content
Glama

X420 agent services

x420_geo_flood-zone

Read-onlyIdempotent

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. Price: $0.05 USDC per call (x402 on Base). This hosted tool does NOT pay and does NOT return the deliverable: it validates the input and returns payment instructions (pay_to, network, price and the x402 URL to pay at). GET the url; read PAYMENT-REQUIRED from the 402; retry with PAYMENT-SIGNATURE (x402 v2). Or run the local x420-mcp server with your own wallet key to pay automatically. Deliverable once paid: JSON: mapped, in_sfha, zones[{zone, subtype, sfha, static_bfe_ft, dfirm_id}].

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 observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only mark it read-only/open-world/idempotent; the description goes far beyond by disclosing that the hosted call does NOT return the deliverable, returns payment instructions instead, requires $0.05 USDC via x402, and spells out the GET → 402 PAYMENT-REQUIRED → retry with PAYMENT-SIGNATURE flow plus the local-server alternative. These are exactly the non-obvious traits an agent needs before calling.

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?

Purpose, source, and price are front-loaded, and the payment sequence is stated step by step. The legal/medical/financial disclaimer sentence is boilerplate that dilutes density, but the remaining content is information-bearing rather than padded.

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?

Although there is no output schema, the description enumerates the paid deliverable's JSON fields (mapped, in_sfha, zones[...]) and fully explains the payment handshake and an alternative execution path. For a two-parameter hosted metered tool, nothing an agent needs to call it correctly 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 both lat/lon already carry descriptions, so the baseline applies. The description only implies 'a coordinate' and adds no format guidance for the string-typed lat/lon, so it contributes no meaning beyond 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?

States a specific resource and scope: 'FEMA flood zone at a point: Flood hazard zone(s) intersecting a coordinate' from NFHL layer 28, and enumerates the returned fields (zone, subtype, SFHA flag, static BFE). This is unmistakably distinct from siblings like x420_geo_elevation or x420_geo_geocode.

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 clear applicability (point-based flood hazard lookup), a price and payment path, and a caveat that it is not an official determination. It does not explicitly route the agent away from similar tools (e.g. storm or hail history siblings) or state when-not-to-use, so it stops short of full alternative guidance.

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.

Resources