Skip to main content
Glama
Sign In
MAQAMI Travel

MAQAMI Travel

by negm17111995
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Find bookings by email and last name

listBookings
Read-onlyIdempotent

Retrieve a customer's hotel bookings by matching their booking email and last name; both must match to return booking IDs, status, hotel, dates, guests, price, and cancellation policy.

Instructions

Find a customer's hotel bookings by the email address and last name used to book.

Both must match the booking holder; nothing is returned otherwise. Returns each booking with its bookingId, status, hotel, dates, guests, price and cancellation policy.

To look up, change or cancel one booking, use its bookingId with the same email in the booking tools.

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": {
      "email": "<email>",
      "lastName": "<lastName>"
    },
    "name": "listBookings"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesThe email address used to make the bookings.
lastNameYesThe booking holder's last name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.0.6
    • removedInput schema / properties / clientReference
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / customTags
      Removed value: -{
-  "description": "Filter by customTags. Comma-separated `KEY:VALUE` pairs (e.g. `SOURCE:GOOGLE,TIER:GOLD`); all pairs are joined with AND. Keys must match `^[A-Z0-9_-]+$`, up to 5 keys, value up to 255 characters. Value matching is case-insensitive.",
-  "type": "string"
-}
    • addedInput schema / properties / email
      Added value: +{
+  "description": "The email address used to make the bookings.",
+  "type": "string"
+}
    • removedInput schema / properties / guestId
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / lastName
      Added value: +{
+  "description": "The booking holder's last name.",
+  "type": "string"
+}
    • removedInput schema / properties / timeout
      Removed value: -{
-  "description": "request timeout in seconds",
-  "type": "number"
-}
    • addedInput schema / required
      Added value: +[
+  "email",
+  "lastName"
+]
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds genuine behavior beyond that: both credentials must match or an empty result is returned, plus the shape of what comes back. It stops short of discussing rate limits or pagination for multi-booking results.

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?

Three short sentences, front-loaded with the core purpose, then the match constraint, then the result shape, then the routing hint. No filler or restatement of the title.

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?

There is no output schema, so the description compensates by enumerating the returned fields (bookingId, status, hotel, dates, guests, price, cancellation policy). Combined with the match precondition and sibling routing, 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds the conjunctive semantics — both email and lastName must match the booking holder and are not alternatives. That is meaningful behavior not derivable from the two independent properties.

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 ('Find'), resource ('a customer's hotel bookings') and the exact lookup keys ('email address and last name used to book'). This clearly separates it from ID-based siblings like get_bookings_bookingid and the booking-management tools.

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?

Explicitly states the match precondition ('Both must match the booking holder; nothing is returned otherwise') and routes the agent to the alternative path for single-booking operations ('To look up, change or cancel one booking, use its bookingId with the same email'). When-to-use and when-to-use-something-else are both covered.

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