swath-mcp
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_stormsA | List radar-verified hail/wind storm events (hail measured by NOAA radar, wind from measured NWS gust and damage reports — never forecasts). Returns storm ids usable with get_swath_report and show_swath_map. |
| get_swath_reportA | ★ The Swath Report: every property inside a storm swath, each scored with the hail size measured at that location (exposure.hail_in, exposure.score 0-1). Bills 1 credit per property returned +25/fresh-fetched record (10 min); preview with get_report_quote. |
| get_report_quoteA | Cost preview for get_swath_report (1 credit): counts cached properties matching the filters without returning rows, plus a clearly-labeled estimate of fresh-fetchable records. Billing always uses actual counts. Use before pulling large reports. |
| email_reportA | Email a swath report summary (max hail/wind, swath area, county, affected-property count, storm link) to your account email — the address your API key was signed up with; no other recipients possible. Summary bills 1 credit (like get_report_quote); pass limit to also include the top N properties by exposure, billed like get_swath_report (1 credit/property + fresh surcharges, 10-credit minimum). |
| lookup_propertyA | Full property record for one address (or lat/lng, or parcel id): year built, sqft, roof age and how it was derived, owner-occupancy, assessed value. Costs 2 credits. |
| create_monitor | Watch a coverage area. Get an email at your account address and/or a signed webhook when a radar-verified storm crosses it. Provide email_alerts: true and/or webhook_url (at least one). With webhook_url, the response includes webhook_secret ONCE — store it. |
| list_monitorsA | List your registered coverage monitors. |
| show_swath_mapA | A storm swath's polygon as GeoJSON (render it on any map) plus severity stats and a viewer URL. |
| get_usageA | Your API plan, credits used this month, and rate limit. |
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 8 tools
Each tool targets a clearly distinct action: finding storms, pricing a report, fetching report data, mapping a swath, emailing a summary, looking up a property, listing monitors, and checking usage. The close pairing of get_swath_report and get_report_quote is resolved by the quote tool explicitly costing without returning rows.
All tool names follow a consistent verb_noun snake_case pattern (get_swath_report, find_storms, list_monitors, show_swath_map). Verb choices match their actions and no mixed casing or stylistic drift is present.
Eight tools is well-scoped for a storm-swath data API. Each tool earns its place covering discovery, quotation, retrieval, visualization, delivery, property lookup, account state, and usage.
The core workflow of finding a storm, quoting and fetching a swath report, viewing it on a map, and emailing a summary is well covered. The main gaps are that list_monitors has no corresponding create/update/delete tools, and there is no dedicated storm detail endpoint beyond find_storms.