Skip to main content
Glama

Stratalize Intelligence

Get Climate Risk Score

get_climate_risk_score
Read-only

Use when pricing physical climate risk for a location — real estate acquisition, commercial property underwriting, construction site selection, or climate-related financial disclosure. Returns a composite risk score across six perils (flood, hurricane, tornado, wildfire, extreme heat, freeze) using the same risk factors embedded in FEMA's National Risk Index. Example: Miami-Dade FL — EXTREME overall, top 2% hurricane exposure, Zone AE flood designation across 40% of commercial parcels, 94 days above 95°F annually — commercial property insurance costs 3.2x national median. Source: NOAA Climate Normals, FEMA National Risk Index, USGS Natural Hazards composite. $0.10 USDC per call.

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": {
      "location": "<location>"
    },
    "name": "get_climate_risk_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationYesUS city and state (e.g. Miami FL or Houston Texas)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds real value beyond that — quantitative cost ($0.10 USDC per call), upstream data provenance (NOAA, FEMA NRI, USGS), and the fact that FEMA NRI risk factors are reused — but it does not discuss latency, coverage limits (US only is implied, not stated), or score interpretation beyond the sample.

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 with the 'Use when…' clause, followed by return contents, sources, and price — good information ordering. The extended Miami-Dade example is long but earns much of its space by demonstrating output shape in the absence of an output schema, though it is denser than strictly necessary.

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 a single required parameter, no output schema, and annotations covering the safety profile, the description does the heavy lifting well: it explains what comes back (composite score plus per-peril detail), where the data originates, and what it costs. It leaves the output contract informal (categorical scale such as EXTREME is only shown by example) and never states that coverage is restricted to US locations.

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?

Only one parameter, and the schema covers it at 100% ('US city and state (e.g. Miami FL or Houston Texas)'). The description's example uses 'Miami-Dade FL', hinting county-level identifiers may be accepted, but this granularity difference is never reconciled with the schema's 'city and state' wording, so the added meaning is marginal and slightly ambiguous. Baseline 3 is appropriate.

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?

A specific verb+resource: returns a composite physical climate risk score for a US location across six named perils (flood, hurricane, tornado, wildfire, extreme heat, freeze). The stated use cases — property underwriting, site selection, financial disclosure — make the scope concrete and distinguish it from benchmark-style siblings such as get_climate_risk_benchmark or get_weather_delay_risk without needing to open their schemas.

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 explicitly declares when to use it ('Use when pricing physical climate risk for a location') and lists four concrete triggering scenarios. It stops short of stating when not to use it or naming an alternative tool for comparison/benchmark cases, which is the only missing piece for a top score.

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