Skip to main content
Glama

get_trip

Full verified record for one trip by slug: itinerary, prices, departures, hotels, trains, inclusions, honest notes, FAQ.

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": {
      "slug": "<slug>"
    },
    "name": "get_trip"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses the record's payload ('full verified record', 'honest notes'), which is genuinely useful, but says nothing about read-only semantics, behavior on an unknown slug, or whether prices/departures are live data.

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 front-loaded sentence fragment with no filler; the verb and resource come first and the content enumeration follows. The list of contents is dense but each item conveys what the agent will receive.

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?

For a one-parameter read tool with no output schema, the description adequately compensates by enumerating the returned fields. Minor gaps remain around failure modes for invalid slugs, which matter little for a simple lookup.

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?

One required parameter with 0% schema description coverage. The phrase 'by slug' confirms the parameter is an identifier rather than free text, but adds little meaning beyond the parameter name 'slug' itself — no format, example, or source of the slug.

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 ('get'), a specific resource ('one trip'), and the identifier type ('by slug'), then enumerates the record's contents (itinerary, prices, departures, hotels, trains, inclusions, notes, FAQ). It implicitly distinguishes itself from search_trips/compare_trips by being a single-trip fetch, though it never names those alternatives.

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 only implied: fetch this when you already have a trip slug and need the complete record. There is no explicit when-to-use versus search_trips or compare_trips, and no statement that a slug must be obtained from a prior search.

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