Skip to main content
Glama

노선 경유 정류소

get_route_stops

Retrieve the ordered sequence of stops for a Korean bus route, using direction to return either origin-to-destination or reverse segments.

Instructions

노선이 지나는 정류소를 순서대로 조회합니다. direction이 0이면 기점→종점, 1이면 종점→기점 방향 구간입니다. 정류소가 수십~수백 개일 수 있으니 필요할 때만 호출하세요.

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>",
      "routeId": "<routeId>"
    },
    "name": "get_route_stops"
  }
}

Input Schema

NameRequiredDescriptionDefault
routeIdYes노선 ID. search_routes 등에서 얻음. 예: 'DJB30300041'
cityCodeYeslist_cities로 얻은 도시 코드. 예: 25(대전)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does add real value: results are ordered along the route, and the stop count can range from tens to hundreds, which warns the agent about payload size. However, it does not address pagination, truncation, or response format, and it discusses a 'direction' selector that has no corresponding schema parameter, leaving the actual behavior of that claim unclear.

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, front-loaded with the core operation, then the ordering detail, then the cost warning. Nothing is padded, though the middle sentence about 'direction' consumes space on a parameter the schema does not expose.

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 simple two-parameter read with fully documented schema, the description covers purpose, ordering, and result volume, which is largely sufficient. The remaining gap is the unexplained 'direction' concept, which creates ambiguity about whether the tool accepts arguments the schema does not declare.

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 100%, and both parameters (routeId, cityCode) already document their own origin and examples, so the baseline would be 3. The description instead introduces semantics for a 'direction' argument (0=origin→destination, 1=destination→origin) that does not exist in the input schema, which can mislead an agent into supplying an invalid argument and adds no valid meaning beyond the schema.

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 specific verb and resource: retrieving the stops a route passes through, returned in sequence order. It distinguishes the direction of traversal (origin→destination vs. reverse), which is meaningful detail. It does not name the inverse sibling get_routes_at_stop, so sibling differentiation is left implicit.

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 guidance is a caution — '정류소가 수십~수백 개일 수 있으니 필요할 때만 호출하세요' — which implies the response can be large and should not be called speculatively. There is no explicit statement of when this tool is the right choice versus find_nearby_stops or get_routes_at_stop, and no prerequisite conditions beyond the schema's mention of obtaining cityCode/routeId elsewhere.

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