Skip to main content
Glama
socialkim

korea-onegov-mcp

by socialkim

검색어 자동완성

onegov_suggest_keywords
Read-onlyIdempotent

Get actual indexed search terms starting with a given prefix. Use when your search returns zero results to discover correct keywords.

Instructions

입력한 앞글자로 시작하는, 실제 색인에 존재하는 검색어를 돌려준다. 검색 결과가 0건일 때 정확한 용어를 찾는 용도로 먼저 쓰면 좋다.

Args:

  • prefix (string, 필수): 앞글자(예: "청년", "반도체").

  • response_format ('markdown'|'json', 기본 markdown)

Returns: { suggestions: [{ text, doc_type }] }

Examples:

  • "청년" → 청년도약계좌, 청년월세지원, 청년기본법 …

  • 쓰지 말 것: 실제 문서를 찾을 때(→ onegov_search)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
prefixYes검색어 앞글자
response_formatNo출력 형식. 'markdown'은 사람이 읽기 좋은 요약(기본값), 'json'은 API 원본에 가까운 구조화 데이터.markdown
Behavior5/5

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

Adds context that results are from actual index (not arbitrary), and explains return structure with examples. Annotations already indicate safe, idempotent read.

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?

Two concise sentences plus structured args/returns/examples. No filler, all lines add value.

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

Completeness5/5

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

Covers purpose, when/not to use, parameter details, return format, and example. No output schema but return structure is explained adequately.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and description adds real-world context: prefix means 'first characters', response_format defaults, and example usage clarifies expected input.

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?

Description clearly states it returns actual index keywords starting with a given prefix, distinguishing from sibling onegov_search for finding documents.

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

Usage Guidelines5/5

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

Explicitly advises use when search results are zero to find correct terms, and warns not to use for finding actual documents (use onegov_search).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/socialkim/korea-onegov-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server