Skip to main content
Glama

지원사업 지역 목록

list_regions
Read-onlyIdempotent

지원사업 자료가 있는 시·도와 시·군·구 이름 목록. sido 를 주면 그 시·도의 시·군·구만. Region names available for Korean support program lookups.

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
sidoNo시·도(선택)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds one genuinely behavioral fact beyond them: the list is limited to regions that have support-program records, not all Korean administrative regions. It says nothing about ordering, duplicates, or result shape.

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?

Very short and front-loaded: the resource is stated first, then the filter behavior. The Korean/English duplication carries some redundancy, though the English line does help non-Korean readers, so it is not wasted space.

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?

A one-parameter read tool with full schema coverage and no output schema needs little, and the description covers scope and filtering. It leaves open how results are returned (flat list vs. nested province→district hierarchy) and whether region strings are meant to be reused as filter arguments elsewhere.

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 100%, and the single 'sido' parameter is documented. The description goes one step further by explaining the effect of supplying it (returns only that province's cities/counties), which adds meaning beyond the terse '시·도(선택)' schema text — a modest lift above the baseline.

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 concrete resource ('시·도와 시·군·구 이름 목록') scoped to regions that actually have support-program data, which distinguishes it from data-fetching siblings like get_support_programs. It stops short of explicitly framing itself as the value-lookup step before filtering support programs, so the sibling relationship is only implied.

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?

Describes conditional behavior ('sido 를 주면 그 시·도의 시·군·구만'), which tells the agent how the filter narrows results. However, it never says when to reach for this tool versus get_support_programs, nor that its output supplies valid region values for downstream queries — usage must be inferred.

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.