iQuota Hotels

Get booking

get_booking

Read-onlyIdempotent

Look up a booking made through iQuota, using its reference and the guest email.

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": {
      "booking_reference": "<booking_reference>",
      "guest_email": "<guest_email>"
    },
    "name": "get_booking"
  }
}

Input Schema

Name	Required	Description	Default
`guest_email`	Yes	Guest email used in the booking.
`booking_reference`	Yes	Booking reference returned by book_hotel.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "_getbDictOutput",
+  "type": "object"
+}

Changed2 schema fields changedNov 9, 2026
- addedInput schema / properties / booking_reference / description
```
Added value: +"Booking reference returned by book_hotel."
```
- addedInput schema / properties / guest_email / description
```
Added value: +"Guest email used in the booking."
```
First observedOct 21, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world scope, so the description's ability to add behavior is limited. It does add that the lookup requires the reference plus the guest email, implying an ownership/verification requirement, but says nothing about not-found behavior, rate limits, or what a failed match returns.

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?

A single well-front-loaded sentence with no wasted words. It is arguably too short rather than too long, but the structure is clear.

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?

An output schema exists so return values needn't be explained, and annotations cover the safety profile. However, for a lookup tool with two required identifying parameters, the description omits whether both must match and what happens on a mismatch, which is the main behavioral question an agent would have.

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 both parameters are documented in the schema, so the description adds little beyond repeating that both the reference and the guest email are used. The phrase 'reference returned by book_hotel' usefully points to the origin of the value, but that origin is already stated in the schema's booking_reference description.

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?

States a specific verb (look up) and resource (a booking made through iQuota), and names the two identifying inputs. It doesn't differentiate from siblings such as cancel_booking or get_hotel, but the purpose is unambiguous.

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

Usage Guidelines3/5

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

Usage is implied by the lookup framing and by the guest_email/booking_reference pairing, but there is no explicit when-to-use or when-not-to-use guidance relative to alternatives.

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

All iQuota Hotels tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?