Skip to main content
Glama
Sign In
korean-law-alio-mcp

korean-law-alio-mcp

by scvcoder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

search_ftc_decisions

Search Korea Fair Trade Commission decisions using keywords. Filter by date, sort order, and result count to retrieve relevant rulings.

Instructions

[공정위] 공정거래위원회 결정문 검색.

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": {
      "display": "<display>",
      "page": "<page>",
      "query": "<query>"
    },
    "name": "search_ftc_decisions"
  }
}

Input Schema

NameRequiredDescriptionDefault
displayYes페이지당 결과 개수 (기본값: 20, 최대: 100)
pageYes페이지 번호 (기본값: 1)
sortNo정렬 옵션: lasc/ldes (법령명순), dasc/ddes (날짜순)
apiKeyNo법제처 Open API 인증키(OC). 사용자가 제공한 경우 전달
queryYes검색 키워드 (필수, 예: '담합', '불공정거래', '시정명령')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior2/5

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

Annotations are absent, so the description bears full burden. It does not disclose behavioral traits such as authentication needs (apiKey is optional but not explained), pagination behavior, or result format. Only the basic search function is noted.

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 description is very concise (one sentence), but it lacks essential usage and behavioral context. While not verbose, it is under-informative for an agent to select and invoke correctly without additional cues.

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?

The tool has 5 parameters, required fields, enums, and no output schema. The description does not explain return format, sorting behavior, pagination details, or how to handle apiKey. It is insufficient for complete understanding.

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 100%, so baseline is 3. The tool description adds no extra parameter meaning beyond the schema's own descriptions, which are adequate.

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?

The description clearly states it searches for Korean Fair Trade Commission decision documents ('공정거래위원회 결정문 검색'), with a distinguishing prefix '[공정위]'. It is specific and differentiates from sibling tools targeting other commissions.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., search_acr_decisions, search_nlrc_decisions). There is no mention of context, prerequisites, or exclusions.

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

Deploy Server

Other Tools