Skip to main content
Glama

list_regions

Retrieve map-ready region names for Korea or the world, filtering by administrative level (sido/sigungu) and narrowing districts within a province.

Instructions

지도에 쓸 수 있는 지역 이름 목록(한국 시·도, 시·군·구, 세계 국가 영문명).

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

Input Schema

NameRequiredDescriptionDefault
levelNosido
regionNokorea
withinNo시·군·구 목록을 이 시·도 안으로 좁힌다. 예: ['경기']

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses the content of the result set but not that this is a side-effect-free lookup, whether results are paginated, how large the list is, or how the filtering parameters change the output. For an unannotated tool that is a substantial gap.

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 front-loaded sentence with zero filler; the parenthetical enumeration does real work. It is efficient rather than padded, though it is arguably underwritten given the tool's three parameters.

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

Completeness2/5

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

With no annotations, no output schema, and three parameters including a filtering array, the description should cover return shape and filter semantics. It only tells the agent what names exist, leaving the agent unable to predict the response for a given `level`/`region`/`within` combination.

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 coverage is only 33% (only `within` has a description), so the description must compensate. It does partly by mapping the content categories to the implicit `level`/`region` enums (시·도, 시·군·구, 세계 국가 영문명), but it never explains the `within` narrowing behavior or how the defaults interact.

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?

Names a specific verb+resource (a list of region names) and enumerates exactly what the list contains: Korean provinces/cities, counties/districts, and world countries in English. This lets an agent tell it apart from siblings like suggest_regions or find_data without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description never says when to call this instead of the closely related sibling suggest_regions, nor does it state any precondition (e.g. call this before filtering by region). Usage is only inferable from the parenthetical content list.

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