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

korean-law-alio-mcp

by scvcoder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_ftc_decision_text

Retrieve the full text of a Korean Fair Trade Commission decision using its unique serial number, with optional API key for authentication.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, and the description is minimal—it only states that it gets full text. It does not disclose potential errors, authentication needs (apiKey described in schema but not elaborated), rate limits, or response format, leaving the agent uninformed about behavioral nuances.

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 sentence with no extraneous information. It is efficient, though it could be slightly more informative without losing conciseness.

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 no output schema and no annotations, the description is adequate for a simple retrieval tool but leaves gaps: it does not state the output format, error behavior, or that the ID comes from a search result (schema does). It is minimally complete.

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?

Both parameters have schema descriptions (100% coverage). The description adds no additional meaning beyond the schema, so a baseline score of 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 states the tool retrieves the full text (전문) of FTC decisions. The verb 'get' and resource 'decision text' are specific. Among siblings, search_ftc_decisions is for searching, so this tool is distinct for retrieval by ID.

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?

No explicit when-to-use or when-not-to-use guidance. The context of sibling tools (search_ftc_decisions) implies this tool is for after searching, but no direct exclusions or alternatives are mentioned.

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