Skip to main content
Glama

get_storm_event_history

Read-only

Use when quantifying climate-related financial risk for insurance underwriting, real estate acquisition due diligence, ESG climate risk disclosures, or board-level climate briefings. Returns NOAA's official tally of billion-dollar weather disasters — hurricane, flooding, tornado, wildfire, winter storm — with event frequency, total economic losses, deaths, and trend direction. The same dataset cited by reinsurers, the Federal Reserve Financial Stability Report, and the SEC climate disclosure framework. Example: Texas 10-year history — 31 billion-dollar events, $174B total losses, frequency increasing — highest insured loss exposure of any US state. Source: NOAA NCEI Billion-Dollar Disasters. $0.02 USDC per call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_storm_event_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoUS state name or abbreviation. Omit for national summary.
years_backNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and non-destructive, so safety is covered. The description adds genuinely new operational context — the NOAA NCEI source and a per-call price of $0.02 USDC — which is valuable. However it says nothing about result caps, latency, or what happens for a state with no recorded events.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Sentences are clean and the use-case hook is front-loaded, but the credibility sentence ('The same dataset cited by reinsurers, the Federal Reserve Financial Stability Report, and the SEC...') is promotional padding rather than invocation guidance. The example with hard numbers is useful; the citation list largely is not.

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 no output schema, the description does the work of previewing the return payload: frequency, economic losses, deaths, trend direction. Source and cost are disclosed. The remaining gap is the unspecified range and semantics of years_back, the one parameter the schema leaves bare.

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?

Schema coverage is 50%: state is documented, but years_back carries only a default of 10 with no description. The description partially compensates via the 'Texas 10-year history' example, yet it never states the valid range or maximum for years_back, so the undocumented half remains unexplained.

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 states a specific verb and resource: 'Returns NOAA's official tally of billion-dollar weather disasters' with named event types and named metrics. It is clearly distinguishable from broader siblings like get_climate_risk_score, though it never explicitly names a sibling or contrast case.

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 gives concrete when-to-use triggers: insurance underwriting, real estate due diligence, ESG disclosures, board briefings. There is no explicit when-not guidance and no alternative tool named for adjacent climate-risk questions, but the usage context is unambiguous.

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