Skip to main content
Glama

버스 노선 상세

get_route_info

Retrieve start and end stops, first and last bus times, and service intervals for a Korean bus route using city and route IDs.

Instructions

노선의 기점·종점, 첫차·막차 시각, 배차간격(분: 평일/토요일/일요일·공휴일)을 조회합니다.

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

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.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. The verb 조회합니다 implies a read-only lookup and the field list tells the agent what comes back, but there is no disclosure of error behavior for invalid routeId/cityCode, no rate-limit or auth context, and no statement about data freshness.

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?

A single well-formed sentence that front-loads the returned fields with no filler. It is appropriately sized for a simple two-parameter lookup, though the parenthetical headway breakdown is slightly dense.

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?

With no output schema, the description usefully compensates by enumerating the returned fields, and the input schema fully documents both required parameters. What remains missing is only minor: no guidance on error cases or on how the headway values should be interpreted.

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%: both routeId and cityCode are documented with provenance (search_routes, list_cities) and concrete examples. The description adds nothing about the parameters, so the baseline 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?

The description names a specific verb (조회합니다) and enumerates the exact resource attributes returned: origin/terminus, first/last departure times, and headway by weekday/Saturday/Sunday-holiday. This clearly separates it from siblings like get_route_stops or get_bus_arrivals, though it never names those alternatives explicitly.

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 only implied by the field list — an agent can infer 'call this when you need schedule/headway data for a known route'. There is no explicit when-to-use statement, no prerequisite note (e.g. that routeId must first come from search_routes), and no mention of when a sibling would be preferable.

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