Skip to main content
Glama

도시 코드 조회

list_cities

Retrieve the cities and city codes supported by the TAGO bus API, optionally filtered by a city-name query. Use these codes to call other bus tools; Seoul is unsupported.

Instructions

국토교통부(TAGO) 버스 API가 지원하는 도시와 도시 코드(cityCode)를 조회합니다. 다른 버스 도구를 호출하기 전에 cityCode를 알아내는 데 사용하세요. query를 주면 도시명에 해당 문자열이 포함된 것만 돌려줍니다. 서울특별시는 TAGO에서 지원하지 않습니다.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_cities"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo도시명 일부. 예: '청주', '부산'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does disclose a real data-scope limitation (서울특별시 unsupported) that would otherwise cause failed lookups. However, it says nothing about return shape, ordering, or whether the list is static, so an agent still lacks a full behavioral picture.

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?

Four short sentences, each doing distinct work: purpose, routing guidance, filter semantics, and an exclusion caveat. Purpose is front-loaded and nothing is repeated.

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?

For a single optional-parameter lookup tool with no output schema and no annotations, the description covers purpose, prerequisite usage, filter behavior, and a key data limitation. Only the returned fields are left implicit, which is a minor gap given the tool's simplicity.

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 genuine meaning: matching is substring/contains-based ('문자열이 포함된 것만'), and the conditional phrasing implies omitting query returns the full list. That goes beyond the schema's '도시명 일부' note.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('도시와 도시 코드(cityCode)를 조회합니다') and pins the data source to the TAGO bus API. It also distinguishes its role from the sibling bus tools by framing itself as the prerequisite that supplies cityCode.

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?

Explicitly says to call it before other bus tools in order to obtain cityCode, which is a clear when-to-use signal. The Seoul exclusion also warns of a scope boundary, but no alternative source is named for unsupported cities.

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