Skip to main content
Glama

FRNC — Korean Franchise Disclosure Risk Check

서비스·데이터 상태

get_service_meta
Read-only

판정 등급 정의, 핵심 8개 축과 질문, 입력 필드, 함정 코퍼스 수, 법령 실조회 상태, 공정위 API 승인 상태와 활용신청 주소, 개인정보 설계를 돌려줍니다.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety and world-access profile is covered. The description adds the notable behavioral fact that results include live external status (law lookup status, FTC API approval state), which explains the open-world hint. It does not say how fresh or large that status payload is, or whether the approval state can vary between calls, so it adds moderate rather than rich context.

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?

A single dense sentence with no filler, and the most conceptual item (grade definitions) is front-loaded. The comma-separated inventory is efficient but reads as a flat list rather than being grouped logically (e.g. definitions vs. live status vs. design notes), which slightly hurts scanability.

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 parameters, no output schema, and safety fully covered by annotations, the remaining burden is describing what comes back, and the description does that item by item. An agent knows what to expect from a call. It could go further by noting whether this is the recommended first call or how large the response is, but nothing essential is missing.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description spends its space on return content instead, which is the right allocation for a no-arg tool.

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 names a specific resource (service/data metadata) and enumerates exactly what it returns: grade definitions, the eight core axes and questions, input fields, trap corpus size, law lookup status, FTC API approval status and application URL, and privacy design. This makes clear it is the introspection/meta tool, distinct from the domain tools in the sibling list. It stops short of an explicit statement like 'use this first to understand the service', which keeps it from a 5.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of alternatives, and no prerequisites or exclusions. An agent must infer from the content list alone that this is the discovery/status endpoint to call before or alongside domain tools. The enumeration hints at usage but never states it.

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.