nfip-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_claimA | Look up a single NFIP flood claim by its unique claim ID. Args: claim_id: The claim's unique identifier (UUID string). Returns: The full claim record, or an error message if not found. |
| search_claimsA | Search NFIP flood claims with optional filters. All filters are combined with AND; omit any filter you don't need. Args: state: Two-letter US state code, e.g. 'FL', 'NJ'. flood_event: Substring match against the named flood event, e.g. 'Katrina' matches 'Hurricane Katrina'. min_building_payment: Only return claims where the net building payment was at least this amount. year: Year the loss occurred. limit: Max number of results to return (default 10). Returns: A dict with the matching claims and how many were found. |
| claims_summaryA | Get aggregate statistics across claims, optionally filtered to one state. Args: state: Two-letter US state code to filter by. Omit for all states. Returns: Claim count, total and average building payments, and the earliest/latest loss years in scope. |
| list_flood_eventsA | List the distinct named flood events present in the claims data (e.g. 'Hurricane Katrina', 'Tropical Storm Allison'), with claim counts. Returns: A dict mapping each flood event name to its claim count. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: listing flood events, retrieving a single claim, searching claims by filters, and producing aggregate statistics. There is minimal overlap in functionality, and descriptions make the boundaries obvious.
Three tools follow a consistent verb_noun pattern: list_flood_events, get_claim, and search_claims. claims_summary breaks the pattern by using a noun phrase, though it is still clear and readable.
Four tools is a well-scoped size for a read-only NFIP claims data server. Each tool covers a distinct query need without redundancy or bloat.
The surface covers the core read-only workflows: enumeration, single-record lookup, filtered search, and aggregate statistics. Minor gaps exist, such as summary filtering by flood event or year, but these do not create dead ends for common use cases.