Skip to main content
Glama

APICK Business

by app.apick
OverviewDiscussionsAdmin

개인통관고유부호 조회

get_pccc

Retrieve a Korean Personal Customs Clearance Code (PCCC) by transaction ID. req_pccc 로 받은 tx_id 를 입력하면 처리 상태를 확인합니다. 아직 승인 전이면 status 는 pending, message 는 "인증 대기중입니다." 이며 과금되지 않습니다. 승인이 끝나면 서버가 최종 정보를 조회해 DB에 저장하고 개인통관고유부호·주소와 함께 수집 시각 checked_at 을 반환하며 이때 과금됩니다. 조회는 정상 처리됐지만 발급된 부호가 없으면 message 는 "조회된 개인통관고유부호가 없습니다." 이고 과금되지 않습니다. 결과는 24시간 동안 재조회할 수 있고 재조회할 때마다 과금됩니다. [호출당 30포인트]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tx_idYesreq_pccc 응답의 트랜잭션 ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / properties / birthday
      Removed value: -{
-  "description": "생년월일 8자리 또는 주민등록번호 13자리 (새로 접수할 때 필수)",
-  "type": "string"
-}
    • removedInput schema / properties / name
      Removed value: -{
-  "description": "이름 (tx_id 없이 새로 접수할 때 필수)",
-  "type": "string"
-}
    • removedInput schema / properties / phone
      Removed value: -{
-  "description": "휴대전화 번호 (새로 접수할 때 필수)",
-  "type": "string"
-}
    • removedInput schema / properties / provider
      Removed value: -{
-  "description": "간편인증 방식 (새로 접수할 때 필수)",
-  "type": "string"
-}
    • changedInput schema / properties / tx_id / description
      Previous value: -"req_pccc 응답의 트랜잭션 ID. 있으면 상태만 확인합니다."New value: +"req_pccc 응답의 트랜잭션 ID"
    • addedInput schema / required
      Added value: +[
+  "tx_id"
+]
  2. Changed8 schema fields changed
    • removedInput schema / properties / answer
      Removed value: -{
-  "description": "문자(SMS)로 발송된 인증번호 6자리",
-  "type": "string"
-}
    • removedInput schema / properties / auth_key
      Removed value: -{
-  "description": "req_pccc(개인통관고유부호 인증 요청) 응답의 인증 키",
-  "type": "string"
-}
    • addedInput schema / properties / birthday
      Added value: +{
+  "description": "생년월일 8자리 또는 주민등록번호 13자리 (새로 접수할 때 필수)",
+  "type": "string"
+}
    • addedInput schema / properties / name
      Added value: +{
+  "description": "이름 (tx_id 없이 새로 접수할 때 필수)",
+  "type": "string"
+}
    • addedInput schema / properties / phone
      Added value: +{
+  "description": "휴대전화 번호 (새로 접수할 때 필수)",
+  "type": "string"
+}
    • addedInput schema / properties / provider
      Added value: +{
+  "description": "간편인증 방식 (새로 접수할 때 필수)",
+  "type": "string"
+}
    • addedInput schema / properties / tx_id
      Added value: +{
+  "description": "req_pccc 응답의 트랜잭션 ID. 있으면 상태만 확인합니다.",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "auth_key",
-  "answer"
-]
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false), the description discloses critical side effects: per-call charging, re-query charges, DB storage, and state-dependent messages such as '인증 대기중입니다.' and '조회된 개인통관고유부호가 없습니다.' It also states the exact cost of 30 points per call, fully compensating for limited annotation detail.

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?

The description front-loads the core purpose in English and then details statuses, charging, and re-query behavior in Korean. Each sentence adds distinct operational information, though the mixed-language structure and level of detail make it slightly dense. It remains logically organized and scannable.

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 no output schema, the description provides essential response semantics: status field values, example messages, checked_at, and the returned PCCC/address. It covers pending, success, and no-code scenarios along with cost implications. It omits edge cases like invalid tx_id or expired requests, but the core agent-relevant behavior is fully specified.

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?

The schema already fully documents tx_id as the transaction ID from the req_pccc response (100% coverage). The description restates this and adds that it is used to check processing status, but does not provide additional format, length, or constraint details. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb-resource pair: 'Retrieve a Korean Personal Customs Clearance Code (PCCC) by transaction ID.' It clearly positions itself as the counterpart to req_pccc by referencing the tx_id source, distinguishing it from all sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It explicitly ties usage to a prior req_pccc call ('req_pccc 로 받은 tx_id') and explains the relevant states (pending, approved, no code) and the 24-hour re-query window. It does not explicitly name alternative tools, but the relationship to req_pccc makes the usage context unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All APICK Business toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources