Skip to main content
Glama
Sign In
MAQAMI Travel

MAQAMI Travel

by negm17111995
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get hotel booking

get_bookings_bookingid
Read-onlyIdempotent

Look up a confirmed hotel booking by booking ID and email to see status, hotel, dates, rooms, guests, price, and cancellation policy.

Instructions

Look up a confirmed hotel booking: status, hotel, dates, rooms, guests, price and cancellation policy.

Requires the bookingId and the email used to book: the server only returns or changes a booking when they match.

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": {
      "bookingId": "<bookingId>",
      "email": "<email>"
    },
    "name": "get_bookings_bookingid"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesThe email address used to make the booking. The server checks it against the booking before returning or changing anything.
lastNameNoThe booking holder's last name, if the customer gives it. Optional.
bookingIdYesThe unique booking identifier (e.g. '2rSJvdDru')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.0.6
    • changedInput schema / properties / bookingId / description
      Previous value: -"(Required) The unique identifier of the booking you would like to update."New value: +"The unique booking identifier (e.g. '2rSJvdDru')"
    • addedInput schema / properties / email
      Added value: +{
+  "description": "The email address used to make the booking. The server checks it against the booking before returning or changing anything.",
+  "type": "string"
+}
    • addedInput schema / properties / lastName
      Added value: +{
+  "description": "The booking holder's last name, if the customer gives it. Optional.",
+  "type": "string"
+}
    • removedInput schema / properties / timeout
      Removed value: -{
-  "description": "request timeout in seconds",
-  "type": "number"
-}
    • changedInput schema / required
      Previous value: -[
-  "bookingId"
-]New value: +[
+  "bookingId",
+  "email"
+]
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered structurally; the description adds the non-obvious authorization behavior — the server only returns or changes a booking when bookingId and email match. It does not mention rate limits or error behavior when the pair does not match, so it falls 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?

Two tight sentences with the resource and payload front-loaded ahead of the access condition. The second sentence slightly restates the email-verification note already present in the schema, which is a minor redundancy.

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 compensates by enumerating the returned fields (status, hotel, dates, rooms, guests, price, cancellation policy) and states the credential requirement. An agent has everything needed to call it correctly.

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 explains bookingId, email and the optional lastName; the description only restates the two required parameters. It adds no format, matching or fallback detail beyond what the schema carries, so the baseline of 3 applies.

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 ('Look up a confirmed hotel booking') and enumerates the payload (status, hotel, dates, rooms, guests, price, cancellation policy), which cleanly separates it from get_flights_bookings_bookingid and getExperienceBooking. An agent can pick it out of a large sibling list without opening the schema.

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?

The description states the precondition for use (the booking must exist as a confirmed booking and both bookingId and email must match) but never names an alternative tool or when to prefer a sibling such as cancel_hotel_booking or put_bookings_bookingid_amend. Context is clear, exclusions are absent.

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