Skip to main content
Glama

수입 컴플라이언스 종합 판정

assess_import_case
Read-only

품목·상황을 자연어로 받아 수입요건·인증·표시·통관 함정을 3단계로 판정하고 근거 조항과 면책을 반환합니다.

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": {
      "query": "<query>"
    },
    "name": "assess_import_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
factsNopurpose(resale|self_use), channel(direct|agency), price_usd, hs_code, rra_cert_no(적합성평가 인증·등록번호), target_age 등
limitNo
queryYes품목과 상황 설명(예: '중국산 블루투스 스피커를 수입해 판매')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / facts / description
      Previous value: -"purpose(resale|self_use), channel(direct|agency), price_usd, hs_code, target_age 등"New value: +"purpose(resale|self_use), channel(direct|agency), price_usd, hs_code, rra_cert_no(적합성평가 인증·등록번호), target_age 등"
  2. First observed

TDQS

B3.2/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 profile is covered. The description adds genuine unannotated context by stating that output includes legal basis clauses and a disclaimer, implying results are advisory rather than authoritative. It says nothing about latency, how ambiguity or insufficient facts are handled, or how the 3 tiers differ.

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 that front-loads the input, then the judgment scope, then the return content — no filler or repetition. Slightly overpacked with noun lists, but every clause carries informational weight.

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

Completeness3/5

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

For a 3-parameter read-only tool with a nested `facts` object and no output schema, the description does tell the agent what comes back (판정, 근거 조항, 면책). It is still incomplete on the query-vs-facts relationship, on the meaning of the 3 tiers, and on any jurisdictional or scope limits.

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 coverage is 67%, so the schema carries most parameter meaning; the description only reinforces that `query` accepts a free-form item-plus-situation string. It never explains the `facts` object's role relative to `query` (whether facts override or supplement the free text), nor what `limit` (capped at 3) controls.

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 action (3단계 판정) and enumerates the exact compliance dimensions covered — 수입요건, 인증, 표시, 통관 함정 — plus the outputs (근거 조항, 면책), so an agent knows precisely what the tool produces. It does not, however, distinguish itself from narrower siblings such as check_kc_certification or lookup_hs_requirements, which overlap with the listed dimensions.

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?

The only usage signal is that input is '품목·상황을 자연어로' (item/situation in natural language). There is no statement of when to pick this comprehensive assessment over the targeted sibling checks, no prerequisites, and no exclusions for cases the tool does not handle.

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.