Skip to main content
Glama

FRNC — Korean Franchise Disclosure Risk Check

리스크 케이스 목록

list_risk_cases
Read-only

가맹사업법 함정 코퍼스 17건을 위험도·분류·키워드로 걸러 봅니다. 각 케이스에 왜 위험한지, 무엇을 물어야 하는지, 어떤 조문과 대조했는지(law_verified)가 붙습니다.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_risk_cases"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordNo제목·질문에 포함된 말
categoryNo
severityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context: each returned case carries why it is risky, what to ask, and a `law_verified` field noting which statutes it was checked against — valuable since there is no output schema. It omits ordering, pagination, and what an empty result means.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the resource and scope, followed by what each result contains. Nothing is repeated from the schema or annotations, and there is no 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 does the necessary work of explaining the return payload (reason, questions to ask, `law_verified`), which is the main gap it needed to fill for a read-only list tool. Minor omissions remain around filter combination and result ordering, but an agent could call this correctly as written.

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 33% — only `keyword` is documented, while `category` and `severity` rely on enums alone. The description partially compensates by mapping the three Korean filter facets (위험도·분류·키워드) onto the parameters, but it never explains how filters combine (AND/OR) or what severity levels mean in practice.

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 states a specific verb and resource: filter the 17-case franchise-law trap corpus by severity, category, and keyword. The bounded scope ('17건') tells an agent exactly what pool it is querying. It stops short of naming a sibling such as check_franchise_risk to contrast with, so sibling differentiation is left to inference.

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?

Usage is only implied: the filtering facets suggest a browse/narrow-down scenario, but there is no explicit statement of when to pick this over check_franchise_risk or scan_contract_text. No prerequisites or exclusions are given. An agent can guess the browse use case but gets no routing help.

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.