Skip to main content
Glama
Sign In
MAQAMI Travel

MAQAMI Travel

by negm17111995
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get tour booking

getExperienceBooking
Read-onlyIdempotent

Retrieve a tour or activity booking's status, details, and voucher by entering the booking ID and email used to book.

Instructions

Look up a tour or activity booking: status, booking details and the voucher once it is confirmed.

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

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.
bookingIdYesMAQAMI experience booking ID from the booking confirmation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.0.6
    • changedInput schema / properties / bookingId / description
      Previous value: -"Dispatcher booking ID returned from POST /experiences/bookings"New value: +"MAQAMI experience booking ID from the booking confirmation"
    • 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"
+}
    • changedInput schema / required
      Previous value: -[
-  "bookingId"
-]New value: +[
+  "bookingId",
+  "email"
+]
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuine value beyond that by disclosing the identity-verification gate (bookingId + email must match) and that the voucher only appears once the booking is confirmed. Minor oddity: "returns or changes" hints at mutation for a read-only tool, but it describes the server's general check, not this tool's behavior, so it is not a contradiction.

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 tight sentences, front-loaded with the core purpose before the prerequisite. No filler or 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 naming what is returned (status, details, voucher post-confirmation) and the mandatory auth condition. An agent has everything needed to call this 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 documents bookingId, email and the optional lastName, including the match-check behavior. The description largely restates the required-parameter matching rule rather than adding new syntax or format guidance, so the baseline 3 for high coverage 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 ("look up") and resource ("tour or activity booking") and even enumerates the payload (status, booking details, voucher once confirmed). This cleanly separates it from siblings like cancelExperienceBooking and getExperienceBookingCancelPreview without the agent needing to open any 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?

Gives a clear precondition: the `bookingId` and `email` must both be supplied and must match, otherwise the server returns nothing. It does not explicitly name alternatives (e.g. cancelExperienceBooking or the cancel-preview tool) or state when to prefer this over them, so it falls short of a full when/when-not rubric.

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