Skip to main content
Glama

1회 환승 경로 찾기

find_transfer_routes

Finds one-transfer bus routes when no direct route exists by checking stop sequences and directions, returning only valid connections with same-stop or nearby walking transfers.

Instructions

직통 노선이 없을 때, 한 번 갈아타서 가는 경로를 찾습니다(두 구간 이동 정류장 수 합이 적은 순). 출발 정류소를 지나는 노선과 도착 정류소를 지나는 노선의 경유 순서·방향을 대조해서, 실제로 이어지는 경로만 돌려줍니다. 같은 정류소에서 갈아타면 sameStop=true, 근처 정류소로 걸어가 갈아타면 walkM(직선거리, m)을 줍니다. 먼저 find_direct_routes를 쓰고, 결과가 비었을 때 같은 후보 목록으로 호출하세요. 정류장 수 기준이라 실제 소요 시간과는 다를 수 있습니다.

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_transfer_routes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo최대 결과 수. 기본 5
cityCodeYeslist_cities로 얻은 도시 코드. 예: 25(대전)
maxWalkMNo갈아탈 때 걸어서 이동해도 되는 최대 직선거리(m). 0이면 같은 정류소 환승만. 기본 200
toNodeIdsYes정류소 ID 목록. 이름이 같은 정류소(길 건너편 등)가 여러 개면 모두 넣으세요. 최대 5개
fromNodeIdsYes정류소 ID 목록. 이름이 같은 정류소(길 건너편 등)가 여러 개면 모두 넣으세요. 최대 5개

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.4/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 does well: it explains the matching logic (comparing stop sequences/directions of routes through the departure and arrival stops, returning only genuinely connected paths), the sort key, and the two transfer modes surfaced as sameStop and walkM. It also warns that stop-count ranking may diverge from actual travel time. It stops short of covering pagination or how limit interacts with the ranking, which keeps it from a 5.

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?

Five tight sentences, front-loaded with the purpose and precondition, then logic, then output semantics, then a single caveat. Nothing is repeated from the schema and no sentence is 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?

No output schema and no annotations exist, so the description must supply the return-value picture, and it names the two distinguishing fields (sameStop, walkM) plus the ordering. It does not describe the rest of each route result (route identifiers, per-segment detail), leaving a modest gap for a tool with no output schema.

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 the schema already documents cityCode, fromNodeIds, toNodeIds, maxWalkM, and limit in detail. The description adds only marginal meaning on top, mainly tying the returned walkM to the walking-transfer concept and hinting that the node ID lists are candidate sets reused from the direct-route call. Baseline 3 is appropriate.

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?

States a specific action ('한 번 갈아타서 가는 경로를 찾습니다'), the precondition ('직통 노선이 없을 때'), and the ordering rule (sum of stop counts across two segments). This clearly separates it from find_direct_routes 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly prescribes the workflow: call find_direct_routes first, and invoke this tool with the same candidate lists only when that result is empty. The 'when not to use' condition is stated directly rather than implied.

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