Skip to main content
Glama

US Disaster Relief Deadline Sentinel

US county disaster deadlines: free sample

disasters_example
Read-onlyIdempotent

Free sample: a real answer for one county, same shape as disasters_lookup.

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": "disasters_example"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety is covered. The description adds that the result is a real (not mocked) answer for a single fixed county and mirrors disasters_lookup's shape, but it omits whether the sampled county is fixed, whether data is current, and any cost/rate context beyond the word "free."

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?

A single short sentence with no wasted wording, front-loaded with the key qualifier "Free sample." It is terse to the point of being slightly cryptic about what an "answer" is, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return structure need not be explained, and the sibling reference covers shape expectations. Still missing for a demo tool: which county is returned and whether the sample is static, which an agent needs to decide if the output is representative.

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?

The tool takes zero parameters, so the schema imposes no semantic burden and the baseline is 4. The description correctly implies no input is needed to get the sample answer.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says it returns "a real answer for one county, same shape as disasters_lookup," which conveys that it is a demo/sample variant of a sibling tool. However, it never states what the answer actually contains (the title says disaster deadlines) or which county is sampled, so the verb+resource is only half specified.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Calling it a "free sample" implies it should be used to preview output shape before invoking disasters_lookup, and the sibling is named, which helps. But there is no explicit when-to-use or when-not-to-use statement, and no warning that it is not a substitute for real county queries.

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.