Skip to main content
Glama

TravelCargo

Search trips

search_trips

Search active public trips (departing today or later) by origin and destination city. City-name variants are tolerated (e.g. Bombay → Mumbai). Returns up to 20 trips sorted by departure; use "page" for more.

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": {
      "origin": "<origin>",
      "destination": "<destination>"
    },
    "name": "search_trips"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResult page (default 1)
dateToNoOptional ISO date (YYYY-MM-DD) upper bound on departure
originYesOrigin city, e.g. "Berlin"
dateFromNoOptional ISO date (YYYY-MM-DD) lower bound on departure
destinationYesDestination city, e.g. "Mumbai"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the visibility filter (active public only), the temporal filter (departing today or later), fuzzy city matching, the result cap of 20, the sort order, and the pagination mechanism. It omits auth requirements, rate limits, and what happens past the last page, which keeps it short of a 5.

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 matching nuance, then the return shape and pagination hint. Every sentence adds information an agent would otherwise have to guess.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by stating the result count cap, sort order, and pagination. It does not describe the fields present on each returned trip, which is the main remaining gap for a search tool whose results feed downstream calls.

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 genuine meaning beyond the schema: it explains that city-name variants are tolerated (Bombay → Mumbai), which is not stated in the origin/destination schema entries, and it clarifies that 'page' is the mechanism for retrieving beyond the first 20 results.

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 gives a specific verb and resource ('Search active public trips') plus a precise scope ('departing today or later') and the filter dimensions (origin and destination city). An agent can immediately tell this is a filtered list operation, distinct from a single-trip lookup like get_trip or a pricing call like estimate_quote.

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 rather than stated: the agent learns it should supply origin and destination and that only future, active, public trips are in scope. There is no explicit guidance on when to prefer this over get_trip or estimate_quote, and no statement of what to do when no results are returned.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources