Skip to main content
Glama

Direct Hotels

Get hotel details

get_hotel
Read-onlyIdempotent

One hotel in full: address, rating, description, its booking link, and answers to what guests ask (pets, parking, breakfast, pool, check-in and check-out times), each with where and when it was read. Use when the user asks about a specific hotel by name, or follows up on one from search_hotels ("does it have a pool?"). Takes an id, slug or page URL from search_hotels, or a name, with city to narrow a common one; several matches come back as candidates. Holds no prices or availability.

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": {
      "hotel": "<hotel>"
    },
    "name": "get_hotel"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity, to narrow a name lookup.
hotelYesHotel id ("27995"), slug ("27995-maison-proust"), page URL, or name ("Maison Proust").
clientNoOptional: your product or agent name, e.g. "Claude". Not used by the tool; recorded only for the public count of which assistants use the directory.

Output Schema

NameRequiredDescriptionDefault
foundYes
hotelNo
answersNo
candidatesNo

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 declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds value beyond them by disclosing that several matches come back as candidates rather than erroring, and that each fact carries 'where and when it was read' (provenance). It does not describe pagination or result-size limits, keeping it just short of a 5.

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 payload contents, then usage, then accepted inputs, then the exclusion — a logical order with no filler sentences. The long parenthetical amenity list and the dense packing of parameter options make it slightly heavier than necessary, but nothing is wasted.

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-entity read tool with an output schema and full annotations, the description supplies everything else an agent needs: what fields return, how ambiguity surfaces as candidates, accepted identifier forms, and the explicit absence of pricing/availability.

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 coverage is 100% and the schema already documents the accepted id/slug/URL/name forms with examples, so the description's restatement of those forms adds little. The note that `city` narrows a common name is helpful but essentially mirrors the schema's own wording. Baseline 3 is appropriate when the schema carries the semantic load.

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+resource ('One hotel in full') and enumerates exactly what comes back: address, rating, description, booking link, and guest-question answers with provenance. It explicitly contrasts with search_hotels, so an agent can distinguish the detail lookup from the search without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives both trigger conditions ('asks about a specific hotel by name' and the follow-up case 'does it have a pool?') and names the sibling it complements, search_hotels. It also states a hard exclusion — 'Holds no prices or availability' — which prevents misuse for rate queries.

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