Skip to main content
Glama

LocalSpot Trip

trip_plan

A ready day-by-day plan for a city: neighbourhoods per day, timed sights and meals (places locals eat), travel minutes, plus links to open and edit it in the planner, compare where to stay, and see where locals eat. Give the traveller the open_in_planner link.

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": {
      "city": "<city>"
    },
    "name": "trip_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity id or name from list_destinations, e.g. Tokyo, Paris, Seoul
daysNoTrip length; the nearest ready plan (2-4 days) is returned
langNoLanguage of names and notes (default en)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the returned structure (per-day neighbourhoods, timed sights, meals, travel minutes, planner links), which is genuinely useful. It says nothing about cost, rate limits, or what happens when no ready plan exists for the requested city — a real gap given the request_city sibling.

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?

Content is front-loaded: the deliverable is described first, then the required action on the link. The single long sentence is dense but every clause adds information; only the run-on structure costs it a point.

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

Completeness3/5

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

Since there is no output schema, the description rightly explains what comes back, which is the main thing an agent needs. It omits the failure path for unsupported cities and does not distinguish this from building a plan via sibling tools, leaving an agent without a fallback strategy.

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 coverage is 100%, so city, days, and lang are already documented, including the note that the nearest 2-4 day plan is returned. The description adds no format or edge-case detail beyond the schema, so 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 resource and its contents: a ready day-by-day city plan with neighbourhoods per day, timed sights and meals, travel minutes, and edit/compare links. It is clearly a retrieval of a pre-built itinerary rather than a place lookup, which separates it from siblings like sights and find_places, though it never names an alternative explicitly.

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?

The only usage direction is the output-handling instruction 'Give the traveller the open_in_planner link.' There is no statement of when to choose this over sights, find_places, or plan_link, and no guidance for cities without a ready plan, so usage is implied rather than specified.

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