Skip to main content
Glama

Get a trip plan day by day

get_trip_plan
Read-onlyIdempotent

Get the day-by-day stops (places with coordinates) of a Triptime AI ready-made plan found with search_trip_plans. Shows a route card with a link to open the plan.

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": {
      "plan_id": "<plan_id>"
    },
    "name": "get_trip_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYesThe plan id from search_trip_plans.
languageNoLanguage for the card and links: the language the user writes in, when it is one of these (optional, default en).

Output Schema

NameRequiredDescriptionDefault
planNo
errorNo
labelsNoDisplay labels for the trip card in the requested language.

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?

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds useful behavior beyond that: what the response contains (day-by-day stops with coordinates) and that a route card with an open link is produced. It does not cover failure behavior for an invalid or foreign plan_id, which keeps it from 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?

Two sentences, no filler. The core action and scope come first, and the return summary follows, with the dependency on search_trip_plans placed where it is immediately relevant.

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?

With an output schema present, the description need not restate return fields, and annotations plus full schema coverage remove the need to explain safety or parameters. What remains thin is differentiation from the sibling plan_trip_link, which the mention of a link to open the plan only partially addresses.

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 description coverage is 100%, so both plan_id and language are already documented in the schema. The description reinforces the plan_id provenance but says nothing about the language parameter or how the card language is chosen, so it adds no meaning beyond the schema. Baseline 3 applies.

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 names a specific verb and resource (get the day-by-day stops of a ready-made plan) and pins the scope to plans originating from search_trip_plans. It also states the return shape (places with coordinates, a route card with a link), which lets an agent distinguish it from a generic search tool without opening the schema.

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?

It clearly establishes the precondition and workflow context: the plan_id comes from search_trip_plans, so this is a follow-up call after a search. It does not state when not to use it or how it relates to the sibling plan_trip_link, so it stops short of full when/when-not guidance.

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