Skip to main content
Glama

FEMA-listed hotels by state and city

get_fema_hotels_by_state_city
Read-onlyIdempotent

Returns the properties on FEMA's Hotel and Motel National Master List in a US state, optionally narrowed by a partial, case-insensitive city ('york' matches New York and Yorktown), ordered by city then name and paginated with offset, limit (up to 200) and total. Covers the 50 states, DC and the territories FEMA lists. Returns FEMA ID, address and property details, no rates.

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": {
      "state_iso": "<state_iso>"
    },
    "name": "get_fema_hotels_by_state_city"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCase-insensitive partial match on the city name.
limitNoProperties per page, 200 at most.
offsetNoNumber of properties to skip.
state_isoYes2-digits US State ISO Code, format XX

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: result ordering (city then name), pagination with total, the 200 cap, case-insensitive partial city matching, and the fact that no rates are returned.

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?

A single dense sentence plus one short sentence, front-loaded with what is returned and the scope, followed by matching, ordering, pagination and output contents. Every clause carries information; nothing is filler.

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?

With no output schema, the description compensates by naming the returned fields (FEMA ID, address, property details) and excluding rates, and it explains pagination via total. Nothing an agent needs in order to call this correctly is missing.

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 100%, so the baseline is 3, and the description earns an extra point by illustrating substring matching ('york' matches New York and Yorktown) and tying limit/offset to pagination with a maximum of 200. It adds meaning on top of the schema rather than repeating it.

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 the properties on FEMA's Hotel and Motel National Master List'), plus the scope (a US state, optional city) and the exact fields returned. An agent can distinguish it from get_fema_hotels_by_zipcode, get_fema_hotel_by_id and search_fema_hotels without opening any schema.

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?

The state-plus-optional-city framing makes the intended use case clear, and the coverage note ('50 states, DC and the territories FEMA lists') tells the agent where it is valid. It stops short of naming alternatives for zip-based or free-text lookups, so there is no explicit when-not guidance.

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