Gondola AI

Overview Schema Source Related Servers Discussions Admin

get_past_trips

Read-only

Retrieve past hotel stays and flights with dates, confirmation numbers, costs, routes, and seat assignments to answer trip-history and travel-preference questions.

Instructions

Get the user's past trips including hotel stays and flights.

Returns a summary of past travel reservations with dates, confirmation numbers,
status, costs, loyalty programs, routes, airlines, ticket class, miles redeemed, and
historical flight seat assignments when Gondola parsed real row+letter seats from
airline emails. Use this for trip-history questions, including favorite hotels,
frequent routes, past airlines, raw seat-assignment evidence, and favorite-seat or
aisle/window/side/row preference questions.

Requires a Gondola account (API key).

Args:
    limit: Max number of past trips to return, most recent first (default 20). The response
        notes how many more exist; raise this only when the user wants their full history.

Returns:
    Formatted list of past trips, or instructions to connect an account.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 29, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The description goes well beyond the readOnlyHint annotation by disclosing that a Gondola account/API key is required, that historical seat assignments are only included when Gondola parsed real row+letter seats from emails, and that the response notes how many more trips exist. These are meaningful behavioral details an agent needs to manage expectations.

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?

The description is well-structured with a concise summary up front, then a detailed field list, then a use-case sentence, then auth and Args/Returns sections. Every sentence adds useful information and the structure makes it easy to scan.

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?

For a single-parameter read-only tool with an output schema present, the description covers all necessary context: what data is returned, when historical seat data exists, authentication requirements, limit semantics, and fallback behavior when no account is connected. Nothing important is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

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

The input schema provides only a bare 'limit' parameter with a default, and schema description coverage is 0%. The description fully compensates by explaining that limit controls the max number of past trips returned, that results are most-recent-first, and that the limit should be raised only when the full history is requested.

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?

The description clearly states the tool 'Get the user's past trips' and specifies the scope: hotel stays and flights. It enumerates the exact data returned (dates, confirmation numbers, status, costs, loyalty programs, routes, airlines, etc.), making it easy to distinguish from siblings like get_upcoming_trips or search_flights.

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 explicitly says 'Use this for trip-history questions' and lists concrete use cases like favorite hotels, frequent routes, and seat preferences. It does not explicitly name when not to use it or alternatives, but the 'past trips' context and the sibling get_upcoming_trips make the boundary clear.

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