Skip to main content
Glama

FEMA-listed property by FEMA ID

get_fema_hotel_by_id
Read-onlyIdempotent

Returns one property on FEMA's Hotel and Motel National Master List by FEMA ID, or a 404 error when the ID is not listed: name, address, phone, property type, stories and sprinklers, with as_of the date of the list snapshot. Use it to confirm a hotel is fire-safe for reimbursed federal lodging. 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": {
      "fema_id": "<fema_id>"
    },
    "name": "get_fema_hotel_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
fema_idYesFEMA ID of the property as printed on the Hotel and Motel National Master List, two letters followed by digits. Case-insensitive.

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 real value beyond them: the 404 failure mode for unlisted IDs, the exact fields returned, the meaning of `as_of` as a list-snapshot date, and the negative disclosure 'No rates.'

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?

Two sentences plus a two-word exclusion, all front-loaded: what it returns, the error case, the returned fields, the snapshot semantics, then the caveat. Nothing redundant.

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 correctly enumerates the response fields and the 404 case, and explains `as_of`. For a single-parameter read-by-ID tool this covers everything an agent needs to call it and interpret the result.

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% and already documents the two-letters-plus-digits format and case-insensitivity, so baseline is 3. The description adds the failure semantics of the ID (404 when not listed), which is meaning the schema does not carry.

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 one property on FEMA's Hotel and Motel National Master List by FEMA ID') and names the identifier used, which cleanly distinguishes it from the search_fema_hotels and get_fema_hotels_by_state_city/by_zipcode siblings.

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 a clear use case ('confirm a hotel is fire-safe for reimbursed federal lodging'), which tells the agent the context in which this lookup matters. It stops short of naming the alternative to use when the agent lacks a FEMA ID (e.g. search_fema_hotels), so it lacks explicit exclusions.

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