Skip to main content
Glama

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

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly and non-destructive, and the description adds substantial context on top: the exact fields returned (count, losses, deaths, 10-year trend), the authoritative source (NOAA NCEI), cited users, and a per-call price of $0.02 USDC. Cost and provenance disclosures are exactly the kind of detail annotations cannot carry.

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?

Sentences are dense but purposeful: usage, return contents, worked example, provenance, and price each add information. Some promotional framing ('authoritative US climate loss series', 'the fifth consecutive year') is narrative color rather than decision-relevant, and the purpose statement is deferred behind the usage clause.

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?

For a one-parameter read tool with no output schema, the description does the heavy lifting: it enumerates returned fields and the trend context. The remaining gap is temporal coverage — an agent still cannot tell which years are queryable or what happens for an out-of-range year.

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 0% for the single 'year' parameter, and the description never explains it directly — no mention of default 2023, valid range, or whether other years are available. The inline example ('2023 — 28 events...') and the phrase 'annual billion-dollar disaster economics' imply the year selects an annual record, which partially compensates but leaves real ambiguity.

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 verb and resource: it returns NOAA's official annual billion-dollar disaster economics with event count, total losses, deaths, and trend context. An agent can tell what data it produces without opening the schema. It stops short of naming a sibling (e.g., get_climate_risk_benchmark or get_climate_risk_score) to contrast against, so it earns a 4 rather than a 5.

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 contexts — board-level ESG reporting, reinsurance negotiation, infrastructure investment, SEC/TCFD disclosure — which is strong positive guidance. It offers no explicit when-not conditions or named alternative tools for adjacent needs such as modeled climate risk scores, so it falls short of a 5.

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