Skip to main content
Glama

식품·화장품·건기식 요건 판정

check_food_cosmetics
Read-only

수입신고·영업등록·한글표시·광고심의 등 식약처 요건을 판정합니다.

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": {
      "product_name": "<product_name>",
      "kind": "<kind>"
    },
    "name": "check_food_cosmetics"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
purposeNo
functionalNo
product_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description usefully scopes which requirement dimensions get judged, but says nothing about result reliability, whether this is advisory vs. authoritative, or what the verdict looks like.

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 front-loaded sentence with zero filler and the verb and scope stated immediately. It is efficient, though its brevity is partly a symptom of missing content rather than disciplined editing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A four-parameter, three-enum regulatory determination tool with no output schema needs the description to explain the inputs and the nature of the returned verdict; it does neither. An agent must guess what to pass for purpose/functional and what it will receive back.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and it provides no parameter meaning at all. The enumerated domains loosely hint at the kind enum values, but purpose (resale vs self_use) and functional (yes/no/unknown) are never explained in either place.

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?

Names a specific verb (판정합니다, 'determines') plus a domain-scoped resource: MFDS requirements covering import declaration, business registration, Korean labeling, and advertisement review. That enumeration distinguishes it from a generic checker, but it never contrasts with siblings such as assess_import_case or lookup_hs_requirements, which plausibly overlap.

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 explicit when-to-use or when-not-to-use guidance and no named alternative. The listed requirement areas imply the domain, but an agent gets no signal about how this differs from the import-case or HS-requirement tools in the sibling list.

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.