Skip to main content
Glama

실시간 버스 도착 정보

get_bus_arrivals

Query upcoming bus arrivals at a Korean stop by city and stop ID, optionally filter by route, and return minutes remaining and stops away.

Instructions

정류소에 도착 예정인 버스를 도착이 빠른 순으로 조회합니다. nodeId는 search_bus_stops 결과에서 얻습니다. routeId를 주면 해당 노선만 조회합니다. arrivalMin은 남은 시간(분, 반올림), stopsAway는 몇 정류장 전인지입니다. arrivingSoon이 true이면 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>",
      "nodeId": "<nodeId>"
    },
    "name": "get_bus_arrivals"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does so substantially: it defines the result ordering, explains the meaning of arrivalMin, stopsAway and arrivingSoon, specifies a presentation rule ('곧 도착' instead of minutes under 1 minute), and interprets the empty-result case as no in-service arrivals. Gaps remain around invalid-ID or network error behavior, but the core read semantics are well covered.

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?

Five short sentences, front-loaded with the core operation and ordering, then parameter sourcing, then output-field semantics, then the edge case. Nothing is redundant, though the nodeId-provenance sentence partially duplicates the schema and could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must explain return values, and it does: it names the three meaningful fields, their units and rounding, the sub-minute flag, and the meaning of an empty list. For a three-parameter read-only lookup this is sufficient for an agent to call it and interpret results correctly.

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 all three parameters are already documented, including the nodeId provenance example and the cityCode example. The description restates the nodeId source and adds only the filtering effect of routeId ('해당 노선만 조회'), which is modest added meaning over the schema's '특정 노선 ID (선택)'.

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 specific verb and resource ('정류소에 도착 예정인 버스를 ... 조회합니다') plus an ordering guarantee (도착이 빠른 순). It implicitly separates itself from search_bus_stops by naming it as the source of nodeId, but it never explicitly contrasts with get_bus_locations or get_routes_at_stop, which an agent may weigh against it in a live-transit context.

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 guidance is present but parameter-oriented rather than tool-oriented: it says nodeId comes from search_bus_stops results and that supplying routeId narrows the query to one route. It gives no explicit when-not-to-use condition or named alternative for related tasks (e.g. vehicle positions vs. arrival predictions), leaving that inference to the agent.

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