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

korean-law-alio-mcp

by scvcoder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

chain_procedure_detail

Retrieve detailed procedures and costs for Korean legal processes. Chains statutes, comparisons, and forms to answer queries about application steps and fees.

Instructions

[⛓체인] 절차/비용. 법령→3단비교→별표/서식 자동 연쇄. 신청/절차 질문 시.

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

Input Schema

NameRequiredDescriptionDefault
queryYes절차/비용 관련 질문 (예: '여권발급 절차 수수료', '건축허가 신청 방법')
apiKeyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description bears full responsibility. It discloses the automatic chaining behavior ('자동 연쇄') and steps (law->comparison->forms), but does not mention limitations, side effects, or failure modes. Adequate but not thorough.

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?

The description is a single concise sentence in Korean, front-loaded with a bracket identifier. It avoids unnecessary words, but the lack of structure (e.g., bullet points) is acceptable for brevity.

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 two parameters, the description is incomplete. It does not explain what the tool returns, how many steps the chain involves, or any prerequisites. The user would need to infer the output format from the name and description, which is insufficient.

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?

The schema description for 'query' is detailed with examples, but 'apiKey' has no description. Overall schema coverage is 50%, and the description adds context for the query parameter but does not compensate for the missing apiKey documentation. The examples help but cover only half the parameters.

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 it is a chain tool for procedure/cost, linking law to comparison to forms. The Korean text specifies the domain and chaining behavior, distinguishing it from other chain tools by focusing on procedures and costs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when there are application/procedure questions, but does not explicitly state when not to use or mention alternatives among the many sibling chain tools. The guidance is present but not comprehensive.

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