Skip to main content
Glama

Plan a London trip

plan_london_trip
Read-onlyIdempotent

Plan a 1-7 day London sightseeing trip: groups places into days by area, in walking order, with the time each visit takes and the walks or Tube hops between them. Give the places the person wants, or interests to pick the best-loved ones. Returns the days plus a link to the interactive plan on the London Tourist Map (map, opening hours for their dates, lunch stops, booking checklist and printable PDF).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "plan_london_trip"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoNumber of sightseeing days (default 3).
paceNoHow full the days are (default normal).
placesNoPlaces they want to see, by name.
interestsNoThemes to fill the days with: hidden_gems, editors_picks, only_here, nature, thrills, quirky, romantic, family, rainy_day, after_dark, or words like "museums", "markets", "free".
start_dateNoFirst day of the trip (YYYY-MM-DD), to avoid closed days.

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real value beyond them by describing the return payload: the day groupings plus a map link, opening hours for the trip dates, lunch stops, a booking checklist and a PDF. It also implies closed-day avoidance, which explains why start_date matters. It stops short of stating pagination/size limits or what happens when requested places don't fit the itinerary.

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?

Three sentences, front-loaded with the core purpose before the input instruction and the return description. The parenthetical feature list is dense but each item is informative; it could be trimmed slightly without loss.

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

Completeness5/5

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

Sibling tool: with no output schema, the description carries the burden of explaining what comes back, and it does — itinerary days plus accompanying plan artifacts. Combined with the read-only annotations and full schema coverage, an agent has everything needed to call it correctly.

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?

With 100% schema description coverage the schema already documents every parameter, including the day range, the pace enum and the interest vocabulary, so the baseline of 3 applies. The description reinforces the days range and the places-or-interests choice but adds no constraint, format or default information that isn't already in the schema.

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?

Names a specific verb (plan), a specific resource (a 1-7 day London sightseeing itinerary) and the exact output shape: places grouped into days by area, in walking order, with visit durations and transit legs. That input contract (accepts place names or interest themes) already separates it from the two siblings, which are lookup-style tools, without needing to name them.

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?

Usage context is stated clearly: planning a multi-day trip, with the agent explicitly told to supply either the places the person wants or interests from which to pick. No exclusions or prerequisites are given, though — nothing tells the agent what to do when place names are unknown (i.e., call find_london_places first) or when a single place's details are needed (london_place_info).

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