Skip to main content
Glama

LocalSpot Trip

plan_link

A link that opens the local.korea planner with these places and sights loaded, split into days by neighbourhood with hours checked. Give it to the traveller.

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>",
      "picks": "<picks>"
    },
    "name": "plan_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYes
daysNo
langNo
picksYesPlace names or sight names/ids
start_dateNoYYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 does disclose meaningful behavior: it generates a planner link, groups picks into days by neighbourhood, and verifies opening hours. It does not mention what happens with invalid or unresolvable picks, the 30-item / 14-day caps, or whether the underlying hours check can fail or drop places.

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?

Two sentences, front-loaded with the core outcome and the day/neighbourhood/hours behavior. The trailing 'Give it to the traveller' is mildly informal but does add an instruction rather than pure filler.

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?

For a 5-parameter generator with no annotations and no output schema, the description covers the central behavior but leaves significant gaps: the language parameter, the start_date, the option to control day count, and the shape of the returned link. An agent could call it correctly in the common case but would be guessing on the optional parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 40%: city, days, and lang have no schema descriptions, and the description mentions none of them. It only obliquely touches picks ('these places and sights') and days ('split into days'), leaving language selection and start_date anchoring entirely unexplained.

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 states a concrete outcome: a link that opens the local.korea planner with supplied places and sights loaded, split into days by neighbourhood with hours checked. That is specific enough to distinguish it from a plain 'trip_plan' result. It loses a point because the verb is implicit ('a link that opens...') and it never explicitly contrasts itself with the sibling trip_plan tool.

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?

'Give it to the traveller' conveys what to do with the artifact once produced, which is a genuine usage hint. However, there is no guidance on when to choose plan_link over trip_plan, no prerequisites (e.g. that picks must be valid place names/ids), and no exclusions.

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