Skip to main content
Glama

FRNC — Korean Franchise Disclosure Risk Check

가맹사업법 조문 조회

get_law_article
Read-only

법제처 OPEN API 로 실조회해 저장한 가맹사업법·시행령 조문 원문을 돌려줍니다. 예: '제7조'(정보공개서 제공·14일 숙고기간), '제6조의5'(가맹금 예치), '제9조'(허위·과장·예상매출액 산정서), '제12조의4'(영업지역). 시행령은 '시행령 제13조' 처럼 넣습니다.

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": {
      "article": "<article>"
    },
    "name": "get_law_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
articleYes조문 번호 또는 키

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety and external-source profile is largely covered. The description adds that the text is fetched in real time and stored, which explains freshness/provenance, but says nothing about error behavior for a missing or invalid article number.

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?

Front-loaded with the purpose, then compact examples that each clarify the input format. The parenthetical glosses for each article are slightly dense but earn their place by disambiguating what the article covers.

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

Completeness4/5

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

For a one-parameter, no-output-schema lookup tool, the description covers what is returned (article original text), the source, and the input format. The notable remaining gap is what happens when an article is not found or the key is invalid.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and defines the single parameter only as '조문 번호 또는 키'. The description adds real meaning beyond that by giving valid format syntax and multiple concrete examples, including the distinct Enforcement Decree prefix.

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?

States a specific verb and resource: returns the original text of Franchise Business Act and Enforcement Decree articles sourced from the 법제처 OPEN API. This is clearly distinct from brand/contract/risk siblings by virtue of the legal-text resource, though it does not name or contrast any sibling explicitly.

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

Usage Guidelines4/5

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

Gives concrete usage context: pass an article number like '제7조' or use the '시행령 제13조' form for the Enforcement Decree, with examples tied to real provisions. No explicit when-not-to-use or named alternatives, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.