Skip to main content
Glama

HS 10자리 세관장확인 요건

lookup_hs_requirements
Read-only

HS 코드로 세관장확인대상 여부·법령·기관을 판정합니다. 6자리는 요건 판정에 부족합니다.

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": {
      "hs_code": "<hs_code>"
    },
    "name": "lookup_hs_requirements"
  }
}

Input Schema

NameRequiredDescriptionDefault
hs_codeYesHS 10자리 품목코드
directionNoimport

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds real behavioral content beyond them: what the lookup returns (requirement status, statute, agency) and the precision requirement on input. It does not mention authentication, rate limits, or how unknown/unmapped codes are handled.

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?

Two short sentences, front-loaded with the outcome and followed by the input constraint; nothing is padded. The final constraint sentence is slightly terse but does earn its place.

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?

With no output schema, the description reasonably sketches the return content (status, statute, agency). However, for a two-parameter tool it leaves the direction parameter entirely unaddressed and gives no guidance on the shape of the result, so it is adequate rather than complete.

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 50%: hs_code is documented in the schema, but direction (with its enum and default) is not, and the description never mentions it -- so the agent learns nothing about how import vs export changes the judgment. The description does add the semantic point that 10 digits are required, which goes beyond the schema's bare '10자리 품목코드'.

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 gives a specific verb and resource: it judges ('판정합니다') whether an HS code is subject to customs-head confirmation ('세관장확인대상'), plus the governing statute and agency. That is concrete enough to pick it out from siblings like check_kc_certification or check_food_cosmetics, though it never names an alternative to contrast against.

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 only implied by the input ('HS 코드로'), with one useful constraint -- that 6-digit codes are insufficient, effectively mandating a 10-digit code. There is no explicit when-to-use versus the sibling check tools, and no statement about the meaning or effect of the import/export direction.

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.