Skip to main content
Glama

FRNC — Korean Franchise Disclosure Risk Check

두 프랜차이즈 조건 비교

compare_franchise_terms
Read-only

두 프랜차이즈(또는 두 제안 조건)를 총투자·가맹비·인테리어·보증금·로열티·숙고기간·위약금·폐점률·해지 유예기간·가맹금 납부·영업지역으로 나란히 비교하고, 각 조건의 위험 신호와 차이를 돌려줍니다. a·b 객체에 check_franchise_risk 와 같은 필드를 넣으면 됩니다. 어느 쪽이 낫다고 단정하지 않고 차이만 정리합니다.

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": {
      "a": "<a>",
      "b": "<b>"
    },
    "name": "compare_franchise_terms"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYes첫 번째 조건(브랜드명 + 조건 필드)
bYes두 번째 조건(브랜드명 + 조건 필드)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint=false, so safety is covered. The description adds meaningful behavior beyond that: the output is a neutral side-by-side difference report including risk signals per condition, and no verdict is rendered. It does not discuss cost, limits, or output shape in more detail.

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?

Three sentences, front-loaded with the comparison and its dimensions, followed by how to populate the arguments and the neutrality scope. The long field list is dense but earns its place given the unstructured nested-object schema.

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 tool with two free-form nested objects and no output schema, the description explains what to put in each side and what comes back (risk signals and differences). Format-level details of the returned report are not described, but the essentials for a correct call are present.

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% but the schema only says 'object (brand name + condition fields)', which is thin for nested objects. The description compensates by naming the concrete fields to include (총투자, 가맹비, 인테리어, 보증금, 로열티, 숙고기간, 위약금, 폐점률, 해지 유예기간, 가맹금 납부, 영업지역) and pointing at check_franchise_risk's field names, though it leaves value formats/units unspecified.

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?

States a specific verb+resource ('두 프랜차이즈 … 나란히 비교') and enumerates the eleven comparison dimensions, so the agent knows exactly what is compared. It also explicitly carves out a boundary against sibling check_franchise_risk by saying it does not declare a winner, only organizes differences.

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 clear context for use — comparing two franchise brands or two competing proposal terms — and states the scope limit (no recommendation). It does not name an explicit alternative for single-brand risk assessment, but the reference to populating a/b with check_franchise_risk-style fields implies the intended upstream workflow.

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.