F
license-
qualityC
maintenanceProvides falling tree risk intelligence for any US property address.
Property Hazard MCP
by ai.zipquote
Server Details
Flood, wildfire, earthquake, and coastal-storm hazard lookup for a US property.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- ericshenus/us-property-hazard-risk
- GitHub Stars
- 0
- Server Listing
- us-property-hazard-risk
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.4/5.0
Tool DescriptionsA
Average 4.5/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
Only one tool exists, so there is no possibility of confusion with other tools.
Naming Consistency5/5
With a single tool, naming consistency is not applicable, but the name clearly follows a verb_noun pattern.
Tool Count3/5
A single tool feels thin for a property hazard assessment domain; users might expect additional tools for batch processing or detailed breakdowns.
Completeness4/5
The tool covers major hazard types (flood, wildfire, seismic, fault, coastal) and returns a composite score, which is reasonably complete for a single-address assessment, though it lacks batch or historical capabilities.
Available Tools
1 toolassess_property_hazardAssess Property Hazard RiskARead-onlyIdempotentInspect
Assess natural hazard exposure for a single US property address.
Validates and geocodes the address (US Census Bureau geocoder), then looks up FEMA flood zone, wildfire hazard, USGS seismic PGA, active fault proximity, and coastal proximity. Returns a location-only hazard score (0-100) and tier. US addresses only; no building characteristics required.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| address | Yes |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| lat | No | Latitude of the matched address |
| lng | No | Longitude of the matched address |
| sfha | No | Whether the address is in a Special Flood Hazard Area |
| message | No | Explanation of why validation failed, if it did |
| validated | Yes | Whether the address was successfully validated/geocoded |
| flood_zone | No | FEMA flood zone code (e.g. AE, X, VE); null if unavailable |
| hazard_tier | No | Hazard tier label: Low, Moderate, High, or Very High |
| seismic_pga | No | USGS peak ground acceleration in g (ASCE 7-22) |
| hazard_score | No | Deterministic location-only hazard score, 0-100 |
| input_address | Yes | The address as provided by the caller |
| hazard_drivers | No | Up to 5 human-readable factors driving the score |
| wildfire_score | No | Coarse wildfire hazard tier, 0 (none) to 4 (very high) |
| flood_available | No | Whether the FEMA flood zone lookup succeeded |
| matched_address | No | Normalized address returned by the geocoder |
| fault_distance_miles | No | Distance to the nearest known active fault, in miles |
| coastal_distance_miles | No | Distance to the nearest coastline, in miles |
Tool Definition Quality
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds behavioral context beyond annotations: it mentions address validation/geocoding via US Census Bureau geocoder, the specific hazard data sources, and that the score is location-only. Annotations already indicate read-only, idempotent, and non-destructive behavior. No contradictions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very concise: two short paragraphs with no wasted words. It front-loads the main action and then lists details. Every sentence adds value.
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?
Given a single parameter and the presence of annotations and an output schema, the description fully covers what the tool does, its input requirements, the process, and the output format (hazard score 0-100 and tier). No critical information is 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?
Only one parameter (address) with 0% schema description coverage. The description compensates by explaining that the address is validated and geocoded, and implies it must be a US property address. This adds meaning beyond the bare parameter name.
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 clearly states the tool assesses natural hazard exposure for a single US property address. It lists specific hazards (FEMA flood zone, wildfire, USGS seismic PGA, active fault, coastal proximity) and notes it returns a location-only hazard score and tier. The purpose is specific and well-defined.
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?
The description specifies that only US addresses are accepted and that no building characteristics are required. This provides clear guidance on when to use the tool. However, it does not explicitly mention when not to use it or any alternatives, though there are no sibling tools to distinguish from.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Flicense-qualityDmaintenanceProperty intelligence API for US real estate. Returns 16+ data points for any US address: noise levels, wetlands, slope, natural light, powerline proximity, crime rates, property facing direction, zoning, public record, radon risk, natural hazards (earthquake, flood, wildfire), neighborhood demographics, falling tree risk, RF/cell tower exposure, and nearby school.
- Flicense-qualityCmaintenanceProvides free property and parcel intelligence using official US government data APIs, county assessor records, and live listings, with tools for hazard risk checks, affordability calculations, and parcel ranking.
Try in Browser
Your Connectors
Sign in to create a connector for this server.