Skip to main content
Glama

Flood, wildfire, and wind risk for a zip

hazard_risk
Read-onlyIdempotent

What flood, wildfire, and wind risk does this zip code carry? NFIP flood-insurance claims on record (count, payouts, recency, claims per 1,000 housing units), FEMA National Risk Index county scores for flood, wildfire, and wind, and recent significant storm events. Claims are history, not a forecast.

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": {
      "zip": "<zip>"
    },
    "name": "hazard_risk"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYes5-digit US zip code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 the description goes beyond that by framing the scope of the data (county-level NRI, NFIP claims on record) and adding the important interpretive caveat that 'claims are history, not a forecast.' It doesn't mention coverage limits or empty-result behavior, but the interpretation guidance is valuable.

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 as a question, then a compact enumeration of returned data, closing with the key caveat. Every sentence carries information; only the rhetorical question form adds a bit of padding.

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?

With no output schema, the description does the work of describing returns in detail (claim counts, payouts, recency, per-1,000 housing units, NRI scores, storm events), which is exactly what's needed. It stops short of saying what happens for a zip with no claims or how county vs. zip granularity interacts, but an agent can call it correctly.

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?

With 100% schema coverage on the single `zip` parameter, the schema already fully documents the input, so the baseline of 3 applies. The description adds nothing about the zip format or constraints that the pattern/description don't already carry.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the specific resource (flood, wildfire, wind risk) and exactly what data is returned: NFIP claims fields, FEMA NRI county scores, and storm events. It is clearly distinct from the market/rent siblings, though it never names them explicitly.

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 only implied — the agent can infer it's a single-zip risk lookup — but there is no explicit when-to-use, when-not-to-use, or pointer to compare_zips for multi-zip needs. That leaves the routing to the agent.

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