Skip to main content
Glama

US Disaster Relief Deadline Sentinel

US county disaster deadlines lookup (assistance cutoff, IRS postponement)

disasters_lookup
Read-onlyIdempotent

Use this when you need to know, for a US county, whether a federal disaster is declared, until when survivors can apply for FEMA individual assistance, and to what date the IRS postponed tax deadlines. For 1 to 25 county FIPS codes: declarations from the last 18 months, application deadline, IRS postponement with release URL, statutory mandatory extension (120 or 60 days, with reason), days left in the county's time zone. No personal data returned. Not affiliated with FEMA or the IRS. Price: 0.01 USDC per call (x402). Free trial: set free_trial to true (3 calls per day per caller).

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": {
      "fips": "<fips>"
    },
    "name": "disasters_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
fipsYes1 to 25 county FIPS codes (2-digit state + 3-digit county), comma-separated
free_trialNoSet to true to ask for the free trial (3 calls per day per caller, shared with the web route, within a daily cap for the service). Without it, the tool asks for an x402 payment.

Output Schema

NameRequiredDescriptionDefault
dataNoOpenFEMA citation, IRS releases read date, time zone source
noteNoHow to read each field
rulesNoRules applied, with official URL and status; the statute in force (26 U.S.C. 7508A as amended in 2021 and 2025) is listed with what it changes, and the superseded regulation is marked as such
windowNoDeclarations covered
licenceNoLicence of the source data: nom, url, source, attribution (required statement)
resultsNoOne entry per county: fips, county, state, as_of, time_zone, time_zone_split_county, declarations[]: declaration, type, title, incident_type, declared_on, incident_begin, incident_end, designated_area, individual_assistance, assistance_deadline, assistance_open, assistance_days_left, irs {status, postponed_to, days_left, release_url, release_id, other_releases, automatic_relief (when the county is listed in an IRS release: the IRS applies the relief automatically to taxpayers located in the covered area, others call the IRS; null otherwise)}, mandatory_extension_end (date or null), mandatory_extension_days (120, 60 or null), mandatory_extension_reason (plain-English reason, also when null), latest_postponement_end, fema_url
disclaimerNoOpenFEMA statement; not legal or tax advice; not affiliated

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / free_trial
      Added value: +{
      +  "description": "Set to true to ask for the free trial (3 calls per day per caller, shared with the web route, within a daily cap for the service). Without it, the tool asks for an x402 payment.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, and the description still adds real operational context beyond them: a per-call price of 0.01 USDC via x402, a free-trial path with a 3-calls-per-day cap, and 'No personal data returned.' Cost, rate limit and privacy posture are exactly the facts an agent cannot infer from annotations or schema.

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 this when...' trigger, followed by scope, returned content, and commercial terms — a sensible ordering with no filler sentences. It is dense but not padded. Minor redundancy: the free-trial cap appears both here and in the schema description.

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 paid, open-world read tool with an output schema, the description covers everything an agent needs before calling: what is returned, the input cardinality limit, the payment model, the free-trial escape hatch, the data-privacy guarantee, and the non-affiliation disclaimer. Return-value detail is correctly left to the 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?

Schema description coverage is 100% and both parameters (fips, free_trial) are already documented in the schema, including the regex-encoded 1-25 constraint and the free-trial daily cap. The description restates the FIPS range and repeats the free-trial mechanic without adding format, validation, or edge-case detail. Baseline 3 is appropriate when the schema carries the burden.

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?

States a concrete verb+resource pair with unusual precision: per-county FEMA disaster declaration status, individual-assistance application deadline, and IRS postponement date, scoped to 1-25 county FIPS codes. An agent knows exactly what question this answers. It never contrasts itself with the sibling 'disasters_example', so the tool is clear in isolation but not explicitly differentiated.

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?

Opens with an explicit trigger: 'Use this when you need to know, for a US county, whether a federal disaster is declared...' and gives the supported input range (1 to 25 FIPS codes). It does not state when NOT to use it, nor name the alternative tool for adjacent questions, so guidance is clear but not exhaustive.

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.