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

korean-law-alio-mcp

by scvcoder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

search_school_rules

Search school rules (academic regulations) for universities and high schools by keyword, with options to sort by date or name and paginate results.

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>",
      "page": "<page>"
    },
    "name": "search_school_rules"
  }
}

Input Schema

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

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?

No annotations provided. Description fails to disclose behavioral traits such as result format, pagination behavior, or any side effects. Minimal detail beyond the name.

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?

Single sentence, concise but lacks detail. Could include key behavioral info without becoming verbose. Structure is fine but content is sparse.

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 does not mention what the tool returns (e.g., list of rules, metadata). Incomplete for a search tool where return format is crucial.

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%. The input schema already defines parameters clearly (query, display, page, sort, apiKey). Description adds no additional semantic value beyond the schema.

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 the specific verb 'search' and resource 'school rules' (includes U.S. universities, high schools). Unambiguous and distinct from sibling tools like search_law or search_ordinance.

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 on when to prefer this tool over alternatives (e.g., get_school_rule_text, search_all). Does not specify prerequisites or context for invocation.

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