Skip to main content
Glama

직통 노선 찾기

find_direct_routes

Find direct bus routes between Korean stops without transfers, ranked by fewest stops, and identify correct boarding/alighting stop IDs when names match; if empty, use transfer routes.

Instructions

출발 정류소에서 도착 정류소까지 갈아타지 않고 가는 버스 노선을 찾습니다(이동 정류장 수가 적은 순). 이름이 같은 출발·도착 후보를 모두 넘기면, 어느 쪽 정류소에서 타고 내려야 하는지(fromNodeId/toNodeId)까지 판별합니다. 결과가 비어 있으면 직통 노선이 없는 것이니 find_transfer_routes로 환승 경로를 찾으세요. viaTurnaround가 true면 종점에서 회차해 가는 경로라 안내 시 언급하세요.

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": {
      "cityCode": "<cityCode>",
      "fromNodeIds": "<fromNodeIds>",
      "toNodeIds": "<toNodeIds>"
    },
    "name": "find_direct_routes"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityCodeYeslist_cities로 얻은 도시 코드. 예: 25(대전)
toNodeIdsYes정류소 ID 목록. 이름이 같은 정류소(길 건너편 등)가 여러 개면 모두 넣으세요. 최대 5개
fromNodeIdsYes정류소 ID 목록. 이름이 같은 정류소(길 건너편 등)가 여러 개면 모두 넣으세요. 최대 5개

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.2/5.0
Behavior4/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 discloses real behavior: results are sorted by fewest stops passed, candidate stop lists are resolved down to concrete fromNodeId/toNodeId, and a viaTurnaround flag can appear in output with the instruction to mention turnaround-at-terminus routes when guiding users. It does not discuss read-only status, limits, or error behavior, but the returned-flag semantics are valuable since 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose and the no-transfer scope are front-loaded in the first sentence, followed by resolution behavior, the empty-result fallback, and the viaTurnaround caveat in a tight, ordered sequence. Every sentence adds decision-relevant information with no filler.

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?

For a three-parameter, no-annotation, no-output-schema tool, the description covers purpose, ordering, stop resolution, the failure path to find_transfer_routes, and one output flag. What is missing is broader return-shape information (the fields other than viaTurnaround) and any note on empty-vs-partial results beyond the "결과가 비어 있으면" condition.

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 100%, so cityCode, fromNodeIds, and toNodeIds are already fully documented in the schema, including the max-5 and same-name-stop guidance. The description reinforces the candidate-list intent and explains that resolution yields fromNodeId/toNodeId, but adds no syntax or format 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource — finding bus routes from a departure stop to an arrival stop — and scopes it with "갈아타지 않고" (without transferring) plus an ordering rule (fewest stops passed). That directly distinguishes it from the sibling find_transfer_routes, so an agent can tell the two apart without opening either schema.

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?

It gives an explicit fallback rule: empty results mean no direct route exists, so call find_transfer_routes instead. It also instructs the caller to pass all same-named candidate stops, which is genuine usage guidance. It lacks a positive upfront "use this when..." statement or any exclusion relative to other siblings such as search_routes, so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.