Skip to main content
Glama

Stratalize Intelligence

Get Noaa Disaster Economics

get_noaa_disaster_economics
Read-only

Use when establishing the macroeconomic cost of climate risk for board-level ESG reporting, reinsurance negotiations, infrastructure investment decisions, or climate-related financial risk disclosures under SEC or TCFD frameworks. Returns NOAA's official annual billion-dollar disaster economics — event count, total losses, deaths, and historical context showing 10-year trend acceleration. Example: 2023 — 28 events, $92.9B total losses, 12% above the 10-year average — the fifth consecutive year of above-average economic losses. Cited by the Federal Reserve, Treasury, and major reinsurers as the authoritative US climate loss series. Source: NOAA NCEI. $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_noaa_disaster_economics"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNo

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 destructiveHint=false, so safety is covered. Beyond that the description adds genuinely useful non-schema facts: the source authority (NOAA NCEI) and a per-call price of $0.02 USDC, which is a real operational constraint. It says nothing about latency, caching, year-range limits, or whether losses are inflation-adjusted.

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?

It is front-loaded with a clear 'Use when...' clause and includes a compact worked example, which is good structure. However, promotional framing ('Cited by the Federal Reserve, Treasury, and major reinsurers as the authoritative series') consumes space that could have documented the year parameter, and the first sentence is an overlong run-on.

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 describe return contents (event count, total losses, deaths, trend context) and gives a concrete sample response, which covers most of the burden. The material gap is methodological: it doesn't state the loss units or whether figures are nominal or inflation-adjusted, which matters for an economics series.

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?

The single `year` parameter has 0% schema description coverage, so the description must carry it — but it only shows 2023 in an example and never states the valid year range, the default, or what happens for years outside the series. The example implicitly communicates the expected input format, which is some compensation for the schema gap.

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 specific resource and payload: NOAA's official annual billion-dollar disaster economics with event count, total losses, deaths, and 10-year trend context. It is clearly distinct from sibling risk-score or benchmark tools by citing the source (NOAA NCEI) and the exact metric series, though it never names a sibling to route against.

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 trigger scenarios (board-level ESG reporting, reinsurance negotiation, infrastructure investment, SEC/TCFD disclosure) that an agent can match to a request. It stops short of stating when NOT to use it or which sibling to pick for a narrower climate-risk 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