get_my_tripsLook up your upcoming and past hotel bookings/trips on Roomza. Requires connecting your Roomza account.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| past | Yes | ||
| count | Yes | ||
| upcoming | Yes |
Changes observed during successful MCP inspections.
Output schema / properties / past / items / properties / confirmationNumber / descriptionAdded value: +"Booking reference. For stays booked through Roomza this is the supplier reference until the hotel issues its own number"Output schema / properties / past / items / properties / hotelConfirmationCodeAdded value: +{
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "description": "The hotel's own confirmation number; null until the hotel issues it"
+}Output schema / properties / past / items / requiredPrevious value: -[
- "bookingId",
- "hotelId",
- "hotelName",
- "hotelUrl",
- "city",
- "state",
- "checkIn",
- "checkOut",
- "nights",
- "confirmationNumber",
- "bookingPlatform",
- "status",
- "specialRequests"
-]New value: +[
+ "bookingId",
+ "hotelId",
+ "hotelName",
+ "hotelUrl",
+ "city",
+ "state",
+ "checkIn",
+ "checkOut",
+ "nights",
+ "confirmationNumber",
+ "hotelConfirmationCode",
+ "bookingPlatform",
+ "status",
+ "specialRequests"
+]Output schema / properties / upcoming / items / properties / confirmationNumber / descriptionAdded value: +"Booking reference. For stays booked through Roomza this is the supplier reference until the hotel issues its own number"Output schema / properties / upcoming / items / properties / hotelConfirmationCodeAdded value: +{
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "description": "The hotel's own confirmation number; null until the hotel issues it"
+}Output schema / properties / upcoming / items / requiredPrevious value: -[
- "bookingId",
- "hotelId",
- "hotelName",
- "hotelUrl",
- "city",
- "state",
- "checkIn",
- "checkOut",
- "nights",
- "confirmationNumber",
- "bookingPlatform",
- "status",
- "specialRequests"
-]New value: +[
+ "bookingId",
+ "hotelId",
+ "hotelName",
+ "hotelUrl",
+ "city",
+ "state",
+ "checkIn",
+ "checkOut",
+ "nights",
+ "confirmationNumber",
+ "hotelConfirmationCode",
+ "bookingPlatform",
+ "status",
+ "specialRequests"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds value by disclosing the account connection requirement and the scope (upcoming and past bookings), which are behavioral prerequisites not captured in annotations. This exceeds the baseline but does not elaborate on return format or pagination, which is partially covered by the output schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences with no redundancy. The core action is front-loaded, and the additional prerequisite is stated compactly. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only tool with no parameters and an output schema present, the description covers the essential context: what it returns (trips/bookings) and a prerequisite (account connection). It does not describe return fields, but the output schema handles that. Unclear edge cases like what happens without a connection are minor for a tool of this simplicity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the baseline for parameter semantics is 4. The description correctly omits parameter explanations since none exist. Schema coverage is technically 100% (vacuously), so there is no gap to compensate for.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear verb and resource: 'Look up your upcoming and past hotel bookings/trips on Roomza.' This distinguishes it from sibling tools like search_hotels or get_hotel by focusing on the user's own bookings rather than general hotel information. However, it does not explicitly contrast with a sibling, so it falls short of a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides only a prerequisite ('Requires connecting your Roomza account') but no guidance on when to use this tool versus alternatives such as get_hotel or secure_room. It does not state explicit conditions or exclusions, leaving usage context largely to inference. This is a significant gap.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.