Skip to main content
Glama

FRNC — Korean Franchise Disclosure Risk Check

계약서·특약 문구 스캔

scan_contract_text
Read-only

가맹계약서·특약·본부 안내 문구를 텍스트로 받아, 가맹사업법·시행령 별표 2의 불공정 유형(구입강제·지정업체 강제, 과중 위약금, 최고 없는 즉시 해지, 영업지역 침해, 숙고기간 포기, 가맹금 본사 직접 수령, 광고·판촉비 일방 부담, 매출 보장, 영업시간 구속, 과도한 경업금지·갱신 거절, 필수품목 단가 미공개·차액가맹금 일방 인상, 판매가격 구속·재판매가격 유지 강요)과 대조해 확인이 필요한 문구만 짚어 줍니다. 각 항목에 매칭된 원문 인용, 위험 등급, 실조회 법 조문, 왜 위험한지, 본부에 요청할 수정 문구 예시가 붙습니다. 결론은 scan_flagged(확인 필요 문구 있음) / scan_no_match(제시된 패턴에서 잡힌 문구 없음) / scan_text_needed(문구 부족) 세 가지이며, 0건이어도 '안전·문제없음'을 뜻하지 않습니다(not_a_clearance_ko 고정 문장을 항상 돌려줍니다). 문맥·예외 조항 해석이나 위법 판정·계약서 검토를 하지 않습니다.

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": {
      "text": "<text>"
    },
    "name": "scan_contract_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes계약서·특약·본사 안내 문구 전문 또는 확인할 조항(최대 20,000자).
clause_textNotext 의 다른 이름(조항 한두 개만 넣을 때)
contract_textNotext 의 다른 이름(계약서 본문)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), and the description goes well beyond them: it specifies the three possible conclusion codes (scan_flagged / scan_no_match / scan_text_needed), the always-returned 'not_a_clearance_ko' disclaimer, and the warning that zero matches does not mean the contract is safe. It also discloses the per-item payload (quoted original text, risk grade, cited statute, rationale, suggested replacement wording), giving the agent a realistic picture of the response.

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?

It is one dense paragraph, but it is front-loaded with what is compared against what, then the return content, then the outcome codes, then the exclusions. The long parenthetical enumeration of 14 violation types is heavy but each clause carries information; little is filler.

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?

With no output schema, the description carries the burden well by describing the result fields and the three conclusion codes plus the non-clearance disclaimer. Minor gaps remain: alias-parameter behavior and the matching granularity (pattern vs. heuristic) are unstated.

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%, so the text, clause_text, and contract_text aliases are already documented in the schema; the description only implies text input ('텍스트로 받아'). It adds no meaning about aliasing precedence or the 20,000-character limit, so the baseline of 3 is the right ceiling.

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 definition names a specific verb and resource (scanning franchise contract text, addenda, and HQ notices) and enumerates the 14 unfair-practice categories from 별표 2 that it matches against, so an agent knows exactly what the tool does. It also draws a sharp negative boundary ('문맥·예외 조항 해석이나 위법 판정·계약서 검토를 하지 않습니다'), which separates it from risk-assessment and legal-lookup siblings.

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?

Usage context is clear: pass contract or clause text in and get back only the phrases needing confirmation. The description states scope exclusions (no context/exception interpretation, no illegality determination, no contract review), which act as when-not guidance, but it never names an alternative sibling such as check_franchise_risk or compare_franchise_terms for those excluded needs.

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.