Skip to main content
Glama

Search FEMA-listed properties by name and town

search_fema_hotels
Read-onlyIdempotent

Searches FEMA's Hotel and Motel National Master List (fire-safe lodging, required for reimbursed federal travel) by property name and city: every word of q must appear as a plain substring of the name or city, with no fuzzy matching. state narrows to one state; paginated with offset, limit (up to 200) and total. Returns FEMA ID, address, phone and property details, no rates: pair with GSA per diem for the lodging cap.

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": {
      "q": "<q>"
    },
    "name": "search_fema_hotels"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesWords to find in the property name or city, all required, case-insensitive.
limitNoProperties per page, 200 at most.
stateNoRestrict the search to one state or territory.
offsetNoNumber of properties to skip.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description goes further by disclosing the matching algorithm — every word must be a plain substring, no fuzzy matching — plus pagination shape and the presence of a `total` count. It also warns that no rates are returned, which prevents a plausible misuse. Only auth/rate-limit details are absent, which is minor for a public read.

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 core action and scope, then the matching rule, then pagination, then return contents and the per-diem caveat — a logical order with no filler sentences. The single dense block with semicolons is efficient but slightly harder to scan than a short bulleted split.

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 carries the return-value burden and does so: FEMA ID, address, phone, property details, and an explicit note that rates are excluded. Combined with the matching semantics and pagination parameters, an agent has everything needed to call it correctly on the first attempt.

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 would be 3, but the description adds genuinely new semantics: substring-only matching with no fuzziness, all query words required, `state` as a single-state narrowing filter, and `limit` capped at 200 with `offset`/`total` driving pagination. That meaning is not derivable from the schema alone.

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 — searching FEMA's Hotel and Motel National Master List by property name and city — and implicitly separates itself from the ID/state-city/zipcode lookups among its siblings. The parenthetical on fire-safe lodging for reimbursed federal travel adds the domain purpose an agent needs to pick it.

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?

Clear context for when to reach for it (name/city text search over FEMA lodging) and an explicit downstream pairing instruction with GSA per diem for the lodging cap. It stops short of naming the sibling alternatives (get_fema_hotels_by_state_city, get_fema_hotels_by_zipcode, get_fema_hotel_by_id) that an agent should prefer for structured lookups.

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