Skip to main content
Glama

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

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so safety is covered; the description adds value beyond that with data provenance (NOAA, FEMA NRI, USGS), the six-peril scope, and an explicit cost of $0.10 USDC per call, which matters for an agent's decision to invoke. It omits latency, coverage limits (e.g. whether non-US locations work), and result granularity beyond the example.

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?

It is front-loaded with the usage trigger, and each clause — perils, sources, price — carries decision-relevant information. The Miami-Dade example is long and mostly demonstrates output format rather than how to call the tool, which is the one place wording could be trimmed.

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?

For a one-parameter read tool with no output schema, the description covers what is returned (composite score, six perils), where the data comes from, and what it costs — everything an agent needs to decide and call correctly. The illustrative example compensates for the absent output schema.

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?

There is a single parameter with 100% schema description coverage, so the schema already tells the agent to supply a US city and state. The description adds only an implicit hint of granularity by showing a county-level input (Miami-Dade FL) in its example, with no statement about accepted formats or what happens on ambiguous input.

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?

The description names a concrete verb and resource — 'Returns a composite risk score across six perils (flood, hurricane, tornado, wildfire, extreme heat, freeze)' — and enumerates its inputs by source (NOAA, FEMA NRI, USGS). It does not explicitly distinguish itself from the adjacent get_climate_risk_benchmark sibling, so an agent must infer the boundary between a point-location score and a benchmark.

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?

It opens with an explicit trigger ('Use when pricing physical climate risk for a location') backed by four named scenarios: acquisition, underwriting, site selection, and financial disclosure. It stops short of stating when not to use it or naming an alternative tool, so the routing signal is strong but not complete.

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