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

korean-law-alio-mcp

by scvcoder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_acr_decision_text

Get the full text of a Korean Anti-Corruption and Civil Rights Commission (ACRC) decision by providing its serial number. Access complete decision documents for analysis and reference.

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_acr_decision_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes결정문 일련번호 (검색 결과에서 획득)
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?

With no annotations, the description carries full burden for behavioral disclosure. It omits whether the operation is read-only, any required permissions, or side effects. The description only states the output, not behavioral traits.

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 a single sentence, which is concise but too brief. It conveys the essential purpose but omits important details that could be included without verbosity. The structure lacks front-loading of key information.

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

Completeness3/5

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

Given the tool's simplicity (no output schema, few parameters), the description is minimally adequate. It explains the source and type of document but lacks context on when or how to use, and does not discuss return format or limitations.

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 coverage is 100%, so baseline is 3. The schema descriptions for 'id' and 'apiKey' are clear, and the tool description adds no extra meaning beyond what the schema provides.

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?

The description clearly states the tool retrieves the full text of decisions from the Anti-Corruption and Civil Rights Commission (ACRC). Although it does not explicitly differentiate from siblings like get_acr_special_appeal_text, the name and context make the purpose clear.

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 such as get_acr_special_appeal_text or other decision retrieval tools. The description does not indicate prerequisites or typical use cases.

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