Skip to main content
Glama

Tubroom

Check one hotel for a tub room

get_hotel
Read-onlyIdempotent

Look up one hotel by name (optionally with its city) or by its tubroom.com URL. Returns the room type with the tub, the tub type, room extras, where and when it was confirmed, address and its tubroom.com page. If the hotel is not listed, says so and returns close name matches.

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

Input Schema

NameRequiredDescriptionDefault
urlNoA tubroom.com hotel page URL, e.g. https://tubroom.com/gatlinburg-tn/crossroads-inn-suites/.
nameNoHotel name as people write it, e.g. "Crossroads Inn Gatlinburg" or "Hampton Inn Pigeon Forge".
placeNoCity, town or state to narrow the name search, e.g. "Gatlinburg" or "TN".

Output Schema

NameRequiredDescriptionDefault
foundYesTrue when the hotel is on Tubroom.
hotelNoThe matching hotel, or null when none matched.
creditYesAttribution line to show with the answer.
alternativesYesOther listed hotels with similar names (name, town, page).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the description's job is to add context beyond that — and it does, by disclosing the not-found fallback (name suggestions) and enumerating what a hit contains. It does not discuss ambiguity when several hotels share a name, which is the main remaining behavioral unknown.

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, both front-loaded: the first states how to identify the hotel, the second states what comes back and the failure mode. No filler, no repetition of the title.

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

Completeness4/5

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

For a read-only lookup with a full schema, an output schema, and rich annotations, this is nearly complete — the return payload and the not-found path are both covered. The one gap is that with zero required parameters the description never says at least one identifier must be supplied, leaving the all-empty call ambiguous.

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?

Schema description coverage is 100% with worked examples for all three parameters, so the baseline is 3. The description only restates that city optionally narrows a name search and that the URL is an alternative identifier, adding little beyond the schema.

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

Purpose4/5

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

"Look up one hotel" gives a specific verb and a single-resource scope, and the accepted identifiers (name + optional city, or tubroom.com URL) make it distinguishable in practice from search_tub_rooms and list_places. It never names those siblings, so the differentiation is implied by scope rather than stated.

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?

It clearly frames the two lookup paths (name, optionally narrowed by city, or a page URL) and states the miss behavior: the tool says the hotel is not listed and returns close name matches. There is no explicit routing advice telling the agent when to prefer search_tub_rooms over this tool, which keeps it below a 5.

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.