Skip to main content
Glama

실시간 버스 위치

get_bus_locations

Retrieve current bus positions for a Korean transit route, including vehicle number, current stop, and route sequence; an empty result means no buses are operating.

Instructions

노선에서 현재 운행 중인 버스들의 위치(차량번호, 현재 정류소, 노선 내 순번)를 조회합니다. towards는 그 버스가 향하는 종점 방향입니다. 결과가 비어 있으면 운행 중인 버스가 없는 것입니다.

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

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

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 full load and does well: it discloses the return shape (vehicle number, current stop, sequence), explains the otherwise opaque 'towards' field as the terminal direction the bus is heading, and states that an empty result means no buses are operating. Gaps remain around data freshness/realtime lag and whether all vehicles on the route are returned.

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?

Three short sentences, front-loaded with the core action, then the field disambiguation, then the empty-result edge case. No filler and no repetition of the title.

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 exists, so the description must explain return values, and it does—including the ambiguous 'towards' field and the no-bus case. What is missing is realtime behavior (polling expectations, latency) for what is inherently a live-position lookup.

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%, with both routeId and cityCode already documented including examples and provenance. The description adds no format or constraint detail beyond that, so the baseline of 3 applies.

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?

States a specific verb and resource ('현재 운행 중인 버스들의 위치 ... 조회') scoped explicitly to a route, and enumerates the returned fields (차량번호, 현재 정류소, 노선 내 순번). This clearly separates it from stop-centric siblings like get_bus_arrivals or search_bus_stops, though no sibling is named outright.

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 is implied by the scope (you need a route to see live vehicles on it) and the empty-result note tells the agent how to interpret a negative answer. However, there is no explicit when-to-use vs when-not guidance, and no mention that routeId must first come from search_routes (that hint lives only in the schema).

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