Skip to main content
Glama

FEMA-listed properties by ZIP code

get_fema_hotels_by_zipcode
Read-onlyIdempotent

Returns every property on FEMA's Hotel and Motel National Master List in a US ZIP code (five digits or ZIP+4), ordered by name, with FEMA ID, address and property details. A known ZIP with no listed property returns an empty list, an unknown ZIP a 404 error. Fire-safe lodging is required for reimbursed federal travel; no rates, pair with get_gsa_perdiem_by_zipcode.

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": {
      "zipcode": "<zipcode>"
    },
    "name": "get_fema_hotels_by_zipcode"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipcodeYesUS ZIP (12345) or ZIP+4 (12345-6789)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and closed-world, so the description's real contribution is edge-case behavior: empty list for a known ZIP with no listings, 404 for an unknown ZIP, and name ordering. It also names the returned fields; the only missing trait is whether results are paginated or capped.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, zero filler: what it returns first, then edge cases, then the pairing caveat. Every sentence carries distinct information.

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 single-parameter read tool with no output schema, the description supplies return contents, ordering, and both failure modes, plus the rate-lookup gap and where to fill it. An agent has everything needed to call it and interpret the answer.

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?

With one parameter at 100% schema coverage, the schema already documents the five-digit and ZIP+4 formats with examples. The description's 'five digits or ZIP+4' restates the schema rather than adding new meaning, so the baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource ('Returns every property on FEMA's Hotel and Motel National Master List in a US ZIP code') plus ordering, which cleanly separates it from get_fema_hotels_by_state_city, get_fema_hotel_by_id and search_fema_hotels.

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?

Gives concrete context for use (fire-safe lodging required for reimbursed federal travel) and an explicit pairing rule: 'no rates, pair with get_gsa_perdiem_by_zipcode.' It stops short of explicitly routing the agent away from search_fema_hotels or the state/city variant, so the sibling choice is only partly resolved.

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