Skip to main content
Glama

FRNC — Korean Franchise Disclosure Risk Check

브랜드 정보공개서 요약

lookup_brand_disclosure
Read-only

브랜드명 또는 브랜드관리번호로 공정거래위원회 가맹정보 데이터를 조회해 가맹본부·업종·가맹사업 개시일·가맹점 수·계약종료/해지·평균매출액·정보공개서 등록번호를 요약합니다. 이 키는 가맹정보 API 활용신청이 승인되지 않아 지금은 내장 샘플로 응답하며 data_state 와 apply_urls(활용신청 주소)를 함께 돌려줍니다. 승인 전에는 화면의 구조만 참고하고, 실제 값은 가맹사업정보제공시스템에서 확인하세요.

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": "lookup_brand_disclosure"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNo가맹사업 기준년도(기본: 최근 3개년 시도)
brand_codeNo브랜드관리번호
brand_nameNo브랜드명(부분 일치)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

While the annotations already declare readOnlyHint=true and openWorldHint=true, the description adds essential behavior they cannot convey: the data is currently sample-only, the response includes data_state and apply_urls, and values must be verified externally. That is exactly the kind of caveat an agent needs before presenting these values as real.

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 three sentences: purpose first, then the caveat, then what the agent should do instead. It is front-loaded and has no filler, though the list of summarized fields is long enough that the caveat is pushed to the middle.

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?

There is no output schema, and the description compensates by naming the key return fields and the data_state and apply_urls metadata. The only gap is the year parameter, whose role in scoping the summary is not explained in prose, but for a read-only lookup tool this is close to 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?

Schema description coverage is 100%, so the meaning of the year, brand_code, and brand_name parameters (including the partial-match behavior) is already documented in the schema. The description only restates the two lookup keys and drops the year filter entirely, so it adds little beyond the structured fields; a baseline 3 is appropriate.

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 uses a specific verb/resource combination (look up FTC franchise data by brand name or brand management number) and enumerates exactly what is summarized: franchisor, industry, start date, store count, contract termination, average sales, and disclosure registration number. It is clearly distinguishable from siblings like check_franchise_risk or compare_franchise_terms, which perform analysis/rather than lookup, but it never names an alternative 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?

The description gives clear usage context: it states that the API approval has not been granted, so responses are built-in samples, and that real values must be confirmed at the franchise information system. This effectively tells the agent when not to trust the output, although it does not explain how to choose this tool over other lookup or analysis tools.

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.