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

korean-law-alio-mcp

by scvcoder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_public_corp_rule_text

Obtain the complete text of a local public corporation or institution regulation using its serial number. Enables detailed analysis of specific rules from Korean public entities.

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": {
      "id": "<id>"
    },
    "name": "get_public_corp_rule_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes규정 일련번호 (검색 결과에서 획득)
apiKeyNo법제처 Open API 인증키(OC). 사용자가 제공한 경우 전달

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior1/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states the purpose without mentioning authentication needs (despite the apiKey parameter), error handling, or any side effects. The agent lacks critical operational context.

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?

The description is a single concise sentence with a front-loaded category label. Every word is purposeful with zero redundancy.

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?

Given no output schema and the existence of many sibling tools, the description should explain what the returned text contains (e.g., full regulation body, metadata). It is too brief to fully inform an agent, especially compared to more descriptive siblings.

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% (both parameters have descriptions). The tool description adds no additional meaning beyond the schema—it repeats no parameter details. Per guidelines, baseline 3 is appropriate.

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 specifies the verb (조회/inquiry) and resource (지방공사공단 규정 본문) and uses a bracket prefix to distinguish from sibling tools like get_public_institution_rule_text and get_school_rule_text. It is unambiguous and directly states what the tool does.

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?

The description provides no guidance on when to use this tool versus alternatives. With many similar sibling tools (e.g., get_ordinance, get_public_institution_rule_text), the absence of contextual usage instructions or exclusions is a significant gap.

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