Skip to main content
Glama

See Sight Tours

Plan a trip itinerary

plan_itinerary
Read-onlyIdempotent

Use this when a traveler wants a day-by-day plan from a starting city for a number of days (optionally an end city, start date and interests). Returns packaged See Sight Tours trips that fit the route and a day-tour plan from the base city, and lists which prices or dates need a dated quote.

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": {
      "start_city": "<start_city>",
      "days": "<days>"
    },
    "name": "plan_itinerary"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYes
localeNoSite language for links, e.g. 'en' (default) or 'es'.
end_cityNo
interestsNo
start_cityYes
start_dateNoYYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine value beyond that by describing the response shape (packaged trips + day-tour plan) and the caveat that some prices/dates require a separate dated quote rather than being final.

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?

It is a single dense sentence pair with the trigger condition front-loaded ('Use this when...'), followed by the return description. Every clause carries information, though the second half packs two distinct output concepts into one long sentence.

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 no output schema, the description carries the burden of explaining returns and does so at a workable level: packaged trips matching the route, a day-tour plan from the base city, and quote-required items. The structure of the returned day-tour plan is left vague, but nothing critical for calling the tool correctly is missing.

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 only 33%, so the description must compensate; it does partially by clarifying that end_city, start_date and interests are optional and by framing 'days' as the length of the day-by-day plan. It omits the locale parameter entirely and adds no format constraints (e.g. the 1–21 day cap or the YYYY-MM-DD date pattern) beyond what the schema already declares.

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 gives a specific verb+resource ('Plan a trip itinerary' / 'day-by-day plan from a starting city') and states both the inputs it consumes and the two-part output (packaged See Sight Tours trips plus a day-tour plan). It implicitly separates itself from quote-oriented siblings by noting it flags which prices or dates need a dated quote, but it never names an alternative tool explicitly.

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?

'Use this when a traveler wants a day-by-day plan from a starting city for a number of days' is an explicit triggering condition with the optional inputs enumerated. There are no when-not conditions or named alternatives, but the mention of items needing a 'dated quote' gives a soft hand-off signal to the quote sibling.

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