Skip to main content
Glama

KC 인증 유형 판정

check_kc_certification
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>"
    },
    "name": "check_kc_certification"
  }
}

Input Schema

NameRequiredDescriptionDefault
rf_txNo
ac_plugNo
batteryNo배터리 종류/내장 여부
target_ageNo어린이제품 판단용 대상 연령
rra_cert_noNo전파 적합성평가 인증·등록번호(예: R-LARN-00-0210). 있으면 국립전파연구원 DB를 즉시 조회
product_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / rra_cert_no
      Added value: +{
      +  "description": "전파 적합성평가 인증·등록번호(예: R-LARN-00-0210). 있으면 국립전파연구원 DB를 즉시 조회",
      +  "type": "string"
      +}
  2. First observed

TDQS

C2.6/5.0
Behavior2/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 profile is covered. The description adds nothing behavioral beyond that: it does not say what form the verdict takes, how confident/conditional the result is when inputs are 'unknown', or that supplying rra_cert_no triggers an external DB lookup. For a rule-based classification tool this leaves meaningful gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The sentence is front-loaded and free of filler, which is good. However, one sentence is under-specified for a six-parameter decision tool, so brevity here costs more than it saves.

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?

With no output schema, the description carries full burden for explaining what the tool returns (a certification type? a list of required tests?), and it says only that a procedure is 'determined'. It also omits how partial/'unknown' inputs are handled, which is central for a rule-based judge with mostly optional parameters.

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?

Six parameters with only 50% schema description coverage, and the description supplies no parameter meaning at all. Three fields (rf_tx, ac_plug, product_name) are undocumented in both places, and the description never explains how inputs like battery or target_age drive the classification – exactly what the description should compensate for at this coverage level.

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 single sentence gives a specific verb (판정합니다) and a specific resource: which conformity-assessment track (전기용품·생활용품·어린이제품·전파 적합성평가) applies to a product. That is enough for an agent to tell it apart from food/cosmetics or HS-requirement siblings. It stops short of explicitly contrasting with those siblings, so not 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 or when-not-to-use guidance, no prerequisites, and no named alternative. The agent must infer from the category list that this is the routing step before deeper lookups like lookup_hs_requirements 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.