Skip to main content
Glama

KWeather Weather

search_region

Read-onlyIdempotent

국내 지역(광역시·도 · 시·군·구 · 읍·면·동)을 이름으로 찾아 코드를 돌려준다. 예: '종로구', '청운효자동', '부산'. 호출 수로 세지 않는다.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-open-world, so safety is covered. The description adds two genuinely non-structured facts: the tool returns a code rather than a record, and calls are not counted against a quota. It still says nothing about result ordering, partial-match behavior, or why limit exists.

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?

Three short sentences: capability, examples, then one caveat. Nothing redundant, and the core action is front-loaded before the illustrative examples.

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?

With no output schema, the description should clarify the return shape, and it only says 'code' — unclear whether a single match or a list of matches is returned, and what fields accompany each. The quota note is a nice addition, but the limit/pagination story is missing for a search tool.

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

Parameters2/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 parameter meaning and largely does not. The query parameter's intent is conveyed only indirectly through the example names, and the limit parameter (default 10) is never mentioned at all — no hint that results are truncated or how many matches a broad term like '부산' may produce.

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?

States a specific verb (find by name), resource (domestic regions across 시/도, 시/군/구, 읍/면/동), and the return value (the code). Concrete example inputs like '종로구' and '청운효자동' make the resource unambiguous. It does not explicitly distinguish itself from the sibling search_city, which is the main thing keeping it below 5.

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 imply when the tool applies (you have a region name and need its code), but there is no statement of when not to use it or how it differs from search_city. An agent choosing between the two has to guess from the hierarchy wording alone.

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