Skip to main content
Glama
Sign In
Korean Law ALIO MCP

Korean Law ALIO MCP

by workbookbulb863
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

search_ordinance

Search Korean local ordinances and regulations by keyword. Specify region or subject to find relevant rules.

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

Input Schema

NameRequiredDescriptionDefault
queryYes검색할 자치법규명 (예: '서울', '환경')
displayYes페이지당 결과 개수 (기본값: 20, 최대: 100)
apiKeyNo법제처 Open API 인증키(OC). 사용자가 제공한 경우 전달

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided. Description does not disclose any behavioral traits (e.g., read-only, API authentication, rate limits, pagination behavior). Minimal info beyond the search action.

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?

Single sentence, no wasted words. However, front-loading is minimal and could be structured better with separate usage notes.

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?

No output schema. Description lacks information on return format, pagination, error handling, or what constitutes a valid query. For a search tool among many siblings, this is incomplete.

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 the description adds marginal value. The hint to include region name is already implied by schema's example for 'query'. No extra meaning for 'display' or 'apiKey'.

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?

Description states it searches ordinances/rules (자치법규) and recommends including region name. Clear verb and resource, but does not differentiate from sibling tools like search_law or search_alio_regulation_text, which may overlap in scope.

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?

Only recommends including region name ('지역명 포함 권장'), which is a vague usage hint. No explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites.

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