Disaster Deadline Sentinel

disasters_lookup

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 of the last 18 months, application deadline, IRS postponement with release URL, mandatory 60-day period, days left in the county time zone. No personal data. Price: 0.01 USDC per call (x402).

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

Name	Required	Description	Default
`fips`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the 18-month declaration window, the 1-25 FIPS batching limit, that output includes an IRS release URL, a mandatory 60-day period and days-left-in-county-timezone, that no personal data is returned, and that each call costs 0.01 USDC via x402. It omits error/failure behavior and what happens if a FIPS code is invalid or unknown.

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?

Three sentences, front-loaded with the use case followed by output scope and the pricing note, with no filler. The middle sentence is a dense comma-separated list of return fields, which is slightly harder to scan but still earns its space.

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 and no annotations, the description must describe return values, scope limits, privacy and cost — and it does all four. For a single-signature lookup tool the remaining gaps are the multi-FIPS encoding format and failure behavior, which are minor but not negligible.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the only parameter 'fips' is an untyped string, so the description must compensate; 'For 1 to 25 county FIPS codes' adds meaningful cardinality and scope information. It does not explain the encoding for multiple codes in a single string parameter (comma-separated? JSON list?), which leaves a real ambiguity for a batch call.

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 (lookup) and resource (federal disaster declarations, FEMA IA deadlines, IRS postponements for a US county), so the agent knows exactly what it gets back. It does not differentiate from the sibling disasters_example, which is the only thing keeping it from 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?

'Use this when you need to know, for a US county, whether a federal disaster is declared...' is an explicit trigger condition tied to the agent's information need. There is no statement of when NOT to use it, no alternative tool routing, and no prerequisite guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Disaster Deadline Sentinel tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.