Skip to main content
Glama

Start a custom trip plan

plan_trip_link
Read-onlyIdempotent

Create a link that opens Triptime AI and starts planning a custom day-by-day trip for a destination on a real map. Use when no ready-made plan fits, or when the user wants to edit the plan, see it on a map, share it or use it offline.

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

Input Schema

NameRequiredDescriptionDefault
daysNoNumber of days (optional).
languageNoLanguage for the card and links: the language the user writes in, when it is one of these (optional, default en).
destinationYesDestination in English, e.g. "Lisbon".

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 genuinely new behavior: the output is a link that launches an external app experience and supports editing, sharing and offline use. It does not say whether a plan record persists server-side or whether the link expires, which is the remaining gap.

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, zero filler. The capability statement comes first and the usage conditions follow, so an agent can act after reading only the opening clause.

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 and annotations covering safety, the description only needs to convey purpose and triggers, which it does. The one missing piece is the lifecycle of the generated link (persistence, expiry), which matters for an agent deciding whether to regenerate it later.

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 all three parameters are already documented, including the language enum and the 1-21 day bound. The description only echoes 'destination' and says nothing about days or language, so it adds no meaning beyond the schema — the baseline 3 applies.

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?

The description names a specific verb and product ('Create a link that opens Triptime AI and starts planning a custom day-by-day trip') plus the scope ('for a destination on a real map'). It implicitly separates itself from the ready-made plan siblings ('when no ready-made plan fits') without naming them, so an agent can place it but must infer the exact alternative.

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 gives a clear negative trigger ('when no ready-made plan fits') plus four positive triggers (edit, map, share, offline). This is solid when-to-use guidance; it stops short of explicitly naming search_trip_plans or get_trip_plan as the alternative, so the routing is implied rather than spelled out.

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