Skip to main content
Glama

정류소 경유 노선

get_routes_at_stop

Lists bus routes passing a stop, including each route's next stop and direction to distinguish same-named stops; direction data is omitted when more than 20 routes are returned.

Instructions

정류소를 지나는 버스 노선 목록입니다. 각 노선에 이 정류소의 다음 정류소(nextStop)와 향하는 종점(towards)을 붙여 줍니다. 같은 이름의 정류소가 여러 개일 때 어느 쪽 방면인지 구분하는 데 사용하세요. 노선이 20개를 넘으면 방향 정보는 생략됩니다.

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>",
      "nodeId": "<nodeId>"
    },
    "name": "get_routes_at_stop"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYes정류소 ID. search_bus_stops 등에서 얻음. 예: 'DJB8001378'
cityCodeYeslist_cities로 얻은 도시 코드. 예: 25(대전)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are supplied, so the description bears the full load, and it does disclose a real behavioral quirk: direction fields are dropped when a stop serves more than 20 routes. That truncation rule is exactly the kind of thing an agent would otherwise misread as missing data. It does not state whether the call is read-only or how results are ordered/limited beyond that cap.

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?

Four short sentences, front-loaded with what is returned, then enrichment, then usage, then the truncation caveat. Every sentence carries information; the only minor waste is that the enrichment sentence repeats field names already implied by the result list.

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?

There is no output schema, and the description describes the response shape well enough (per-route nextStop and towards) plus the 20-route degradation rule. For a two-parameter read tool that is close to complete; only ordering, and whether maxCount can be configured, remain unstated.

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%: nodeId and cityCode are already documented with examples and provenance (search_bus_stops, list_cities). The description adds nothing about parameter format or the dependency between cityCode and nodeId, 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+resource pair ('정류소를 지나는 버스 노선 목록') and then adds exactly what is attached to each item (nextStop, towards). An agent can distinguish this from route-detail tools like get_route_info without opening the schema, even though no sibling is named.

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 a concrete when-to-use signal: disambiguating which direction/boarding side applies when several stops share a name. It stops short of naming an alternative (search_bus_stops, find_direct_routes) for the case where you want routes without per-stop direction data, so it is clear context without explicit exclusions.

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