Skip to main content
Glama

KWeather Weather

search_city

Read-onlyIdempotent

세계 도시를 한국어 · 영어 도시 이름이나 나라 이름으로 찾아 도시 코드를 돌려준다. 예: 'Tokyo', '파리', '베트남'. major=true 는 주요 160 도시(상품 끝 숫자 2)에도 있는 곳. 호출 수로 세지 않는다.

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": {
      "query": "<query>"
    },
    "name": "search_city"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The description adds genuinely useful context beyond the annotations: it says the call is not counted toward a call quota and that the return value is a city code, which the readOnlyHint/openWorldHint annotations do not cover. Against that, the 'major=true' sentence describes a flag absent from the input schema, which is confusing rather than clarifying.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is front-loaded and efficient, and the examples earn their place. The 'major=true 는 주요 160 도시(상품 끝 숫자 2)' clause is cryptic — it references a product-code digit scheme with no explanation and no matching parameter, so it consumes space without being actionable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter lookup with no output schema, the description covers the essential return type and input examples reasonably well. It is incomplete because 'limit' behavior is undocumented and the dangling 'major=true' reference cannot be acted on from the supplied schema.

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 0%, so the description must carry the parameter meaning; it does explain the key 'query' parameter well by listing the accepted Korean/English city and country name forms with examples. The 'limit' parameter is never explained, and the description references a 'major' parameter that does not exist in the schema, leaving a real semantic gap.

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 states a specific verb and resource ('세계 도시를 ... 찾아') and adds what comes back ('도시 코드를 돌려준다'), so an agent knows this is a lookup that yields a city code. It does not explicitly contrast with the sibling search_region, so it stops just short of full sibling differentiation.

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?

The examples ('Tokyo', '파리', '베트남') make the acceptable query forms concrete, including that country names are valid inputs. However, there is no statement about when not to use this tool or which sibling to prefer for region-level lookups, so usage guidance remains implied rather than explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources