Skip to main content
Glama

과대광고·한글표시사항 검수

check_ad_labeling
Read-only

상세페이지·상품명 문구와 라벨 문구를 품목 유형(일반식품/건강기능식품/화장품/기능성화장품)별로 대조해 질병 효능·의약품 오인·거짓과장·체험기·기능성 오인 등 위험 표현과 한글표시사항 누락 항목을 근거 법령·대체 표현과 함께 반환합니다.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
ad_copyNo상세페이지·상품명·홍보 문구(최대 4,000자)
purposeNo
importedNo수입 제품 여부
functionalNo기능성 여부(화장품이면 기능성화장품)
label_textNo라벨·한글표시사항을 텍스트로 옮긴 내용(최대 4,000자)
label_itemsNo항목별 체크(예: {'product_name': true, 'expiry_storage': false})
product_nameNo제품명(선택). 있으면 수입요건도 함께 판정
product_typeNo품목 유형. 생략하면 문구·제품명에서 판단

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 goes further by disclosing the return content — risk expressions plus 근거 법령 and 대체 표현, and missing 한글표시사항 items — which is valuable since no output schema exists. It stops short of operational details such as the 4,000-character input ceiling or zero-argument behavior.

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 a single dense sentence, but it is front-loaded with the core action and inputs before moving to the returned risk categories and evidence. The enumerated risk list earns its length by telling the agent what kinds of findings come back, though the noun stacking is heavier than necessary.

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 9 parameters, a nested label_items object, and no output schema, the description must carry the return-value burden — and it does, describing findings, legal basis, and alternative phrasing. The remaining gap is what happens when all parameters are omitted, since none are required.

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 78%, so the schema already documents most parameters including the 4,000-char limits and the product_type enum. The description reinforces the product_type taxonomy inline and frames what ad_copy vs label_text mean together, but adds no format or syntax detail beyond the schema. 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 names a specific verb and resource pair (상세페이지·상품명 문구와 라벨 문구를 대조해 ... 검수) and enumerates the risk categories it detects (질병 효능·의약품 오인·거짓과장·체험기·기능성 오인). An agent can tell this is an ad-copy/label compliance checker rather than a certification or HS-code lookup. It does not explicitly distinguish itself from a plausible sibling such as check_food_cosmetics, 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 Guidelines3/5

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

Usage is implied by the named inputs: use it when you have promotional copy and/or label text to screen per product type. There is no explicit when-to-use vs when-not guidance and no alternative tool is named, so the agent must infer the boundary against check_food_cosmetics or get_legal_basis.

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.