get_bus_locationRetrieve real-time locations of buses on a specific route using its route ID. Get the route ID via search_bus_route, then query this tool for live bus positions.
노선 ID(routeId) 기준 그 노선을 운행 중인 버스들의 실시간 위치를 가져온다. routeId는 search_bus_route로 먼저 찾는다.
| Name | Required | Description | Default |
|---|---|---|---|
| routeId | Yes | 노선 ID (search_bus_route 결과의 routeId) |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It states it fetches data but does not disclose any caveats such as empty results, potential errors, or that it is a read-only operation. The description is minimal and does not add context beyond the basic action.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two short sentences, with the primary action front-loaded and the prerequisite clearly stated. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with one parameter and no output schema, the description provides the essential usage steps. It could benefit from noting the return format (e.g., a list of coordinates) but is adequate for its complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already describes the only parameter (routeId) with the same guidance as the description, so the description adds little value. Schema coverage is 100%, warranting the baseline score of 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific action (fetch real-time locations of buses) with a clear resource (route identified by routeId). It distinguishes itself from siblings like search_bus_route and get_bus_arrivals by focusing on current positions, and it explicitly ties to search_bus_route for the prerequisite.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides clear usage context by specifying that routeId must be obtained from search_bus_route first, which is an important prerequisite. However, it does not explicitly state when to use this over other location-related tools like get_bus_arrivals, though the purpose is clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.