Skip to main content
Glama

버스 정류소 검색

search_bus_stops

Search bus stops by city code using a stop name or stop number to retrieve matching stops and node IDs for arrival queries. Matches are ordered exact, prefix, then partial name.

Instructions

도시 코드와 정류소명(또는 정류소 번호)으로 버스 정류소를 검색합니다. 결과는 이름이 검색어와 정확히 일치 → 앞부분 일치 → 포함 순으로 정렬됩니다. 같은 이름의 정류소가 여러 개면 도로 반대편 등 방향이 다른 정류소입니다(get_routes_at_stop으로 방향 확인). 하나의 도시 코드에 인접 시·군이 함께 묶여 있을 수 있습니다. 결과의 nodeId는 도착 정보 조회 등 다른 도구에서 사용됩니다.

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

Input Schema

NameRequiredDescriptionDefault
nameNo정류소명 일부. 예: '시청'
limitNo최대 결과 수
stopNoNo정류소 번호
cityCodeYeslist_cities로 얻은 도시 코드. 예: 25(대전)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.2/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 burden and largely meets it: it discloses result ordering (exact → prefix → contains), explains that same-name hits are opposite-direction stops, warns about multi-city bundling, and notes that nodeId feeds downstream tools. It does not state read-only/safety semantics or what happens when limit truncates results.

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?

Five short sentences, front-loaded with purpose, then ranking, then the duplicate-name caveat, then the city bundling caveat, then the nodeId handoff. Each sentence adds actionable information and none is filler.

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?

For a four-parameter read tool with no annotations and no output schema, the definition covers what an agent needs: how to invoke, how results are ordered, how to interpret duplicates, and how nodeId is reused downstream. Nothing essential for a correct call is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning on top: it clarifies that name matching is partial and ranked, that stopNo is an alternative lookup key to name, and that cityCode may span neighboring cities. limit behavior is left to the schema.

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 (search bus stops by city code plus name or stop number), which is far more than a restatement of the name. It implicitly separates itself from get_routes_at_stop by delegating direction checks there, but never contrasts with find_nearby_stops or search_routes, the closest sibling alternatives.

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 clear routing instruction ('get_routes_at_stop으로 방향 확인') for the disambiguation case and warns that one city code may cover adjacent cities, which prevents wrong-city assumptions. It does not state when to prefer this over find_nearby_stops or search_routes, so no explicit exclusions.

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