Skip to main content
Glama

DealLabs

Plan a local route

plan_local_route
Read-only

Can these stops fit in this time, in this order? Judges each stop with its posted hours on the date. The tool does not guess how long a visit takes: visit_min is required.

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>",
      "stops": "<stops>",
      "date": "<date>",
      "start_time": "<start_time>",
      "visit_min": "<visit_min>"
    },
    "name": "plan_local_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity key, e.g. "seoul".
dateYes
fromNo
stopsYesplace_id values, in order.
end_timeNo
visit_minYesMinutes at each stop.
start_timeYes

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?

readOnlyHint=true already tells the agent this is a safe read, so the bar is lower. The description does add real behavior: hours are evaluated per stop on the specific date, and visit duration is never inferred — visit_min is mandatory. However, it says nothing about what happens on failure (error vs. a per-stop verdict) or the shape of the response, which matters given no output schema exists.

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 short sentences with the core question front-loaded, then the two behavioral constraints. The interrogative framing is slightly informal but it communicates scope quickly. No filler sentences.

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?

Seven parameters (five required), a nested `from` object, and no output schema — this is a moderately complex tool, and the description leaves the agent unsure what the result looks like (a boolean? per-stop feasibility list?) and what end_time vs. start_time do. It covers the conceptual core but not enough of the surrounding contract.

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 only 43%, so the description should be compensating. It reinforces two things the schema already states (stops are ordered, visit_min is per-stop minutes and is required) but leaves date, start_time, end_time, and from completely unexplained in both places. The one genuinely additive note is that the tool will not guess visit length, forcing the caller to supply visit_min.

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 opens with a concrete question ("Can these stops fit in this time, in this order?") that pins down the operation as a feasibility check over an ordered stop list against posted opening hours on a given date. That is a specific verb+resource, distinguishable from search_verified_places or find_active_popups. It stops short of naming a sibling explicitly, so it earns 4 rather than 5.

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?

Usage is implied: you call this when you already have ordered place_ids and a time window and want to know if they fit. There is no explicit statement of when NOT to use it, no mention of prerequisites (e.g. that stops must be verified place_ids), and no routing to alternatives. Adequate but inferential.

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