Skip to main content
Glama
Sign In
MAQAMI Travel

MAQAMI Travel

by negm17111995
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get hotel details

get_data_hotel
Read-onlyIdempotent

Retrieve complete hotel details by hotelId for MAQAMI Travel, including descriptions, amenities, images, location, and ratings for hotel detail or booking pages.

Instructions

Overview

Get comprehensive details about a specific hotel including descriptions, amenities, images, location, and ratings. Perfect for displaying hotel detail pages.

When to Use

  • Hotel detail pages - Show complete hotel information

  • Booking pages - Display hotel details before booking

  • Hotel profiles - Build rich hotel information pages

  • Content display - Show descriptions, amenities, and images

What You Get

  • Complete hotel information - Name, address, description, and ratings

  • Amenities list - All available facilities and services

  • Image gallery - Hotel photos and images

  • Location details - Address, coordinates, and location information

  • Hotel metadata - Star rating, chain information, and classifications

Quick Start

Provide the hotelId as a query parameter. Returns complete hotel details including all metadata, amenities, and images.

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": {
      "hotelId": "<hotelId>"
    },
    "name": "get_data_hotel"
  }
}

Input Schema

NameRequiredDescriptionDefault
hotelIdYesUnique ID of a hotel
timeoutNorequest timeout in seconds
languageNoThe language code, indicating in which language the results should be returned. e.g. 'fr'
advancedAccessibilityOnlyNoIf `true`, accessibility section will be returned

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds useful return-shape context (what fields come back) but says nothing about rate limits, error conditions, or behavior when hotelId is invalid/unknown. With annotations carrying the safety load, this is adequate but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is heavily padded with Markdown headers and bullet lists that restate the same idea four times ('What You Get' re-lists what the Overview already named; the four 'When to Use' bullets are near-duplicates). Front-loading is fine, but a large share of the text does not earn its place.

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

Completeness3/5

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

There is no output schema, and the description does a reasonable job enumerating the returned fields, which is the main thing an agent needs here. Still missing is any differentiation from the crowded hotel-sibling set, which is the key context gap for this tool.

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%, so the schema already documents hotelId, timeout, language, and advancedAccessibilityOnly. The description only reaffirms that hotelId is required and passed as a query parameter; it adds no format, default, or interaction detail (e.g., what advancedAccessibilityOnly changes) beyond the schema, so the baseline of 3 applies.

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?

The overview states a specific verb+resource: fetch comprehensive details for a specific hotel (description, amenities, images, location, ratings). That is clear enough to act on. However, it never distinguishes itself from the many hotel siblings (get_data_hotels, get_data_hotel_search, get_data_hotel_ask, get_data_hotels_room_search), so an agent cannot tell which one to pick for detail retrieval.

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

Usage Guidelines2/5

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

The 'When to Use' list gives four bullets that all say the same thing – display hotel detail/booking/content pages – with no conditions that select this tool over its search/list siblings. There are no exclusions, prerequisites, or named alternatives, so it provides no routing help.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools