Skip to main content
Glama

eKYC 본인확인

kyc_verify
Read-only

Verify identity with an ID photo and a short selfie video or photo: ID screen-capture/editor detection, real-person liveness (turning the head left and right), and face match against the ID. Requires a single-use capture session from /rest/kyc_session. 신분증 사진과 좌우로 고개를 돌린 짧은 촬영 영상(또는 사진)으로 신분증 위조·화면 캡처, 실제 사람의 움직임, 신분증 얼굴과의 일치를 한 번에 판정합니다. 촬영 세션(/rest/kyc_session) 서명이 필요합니다. [호출당 200포인트]

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": {
      "session": "<session>",
      "document_image_url": "<document_image_url>",
      "face_video_url": "<face_video_url>",
      "face_image_url": "<face_image_url>"
    },
    "name": "kyc_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionYes촬영 세션 서명(/rest/kyc_session 발급 → /rest/kyc_seal 서명)
thresholdNo얼굴 일치 기준 점수 (범위: 0.2 ~ 0.8, 기본값 0.4)
face_image_urlYes다운로드 가능한 https URL (허용 형식: image/jpeg, image/png) (최대 50MB)
face_video_urlYes다운로드 가능한 https URL (허용 형식: video/mp4, video/quicktime, video/webm, video/3gpp) (최대 30MB)
document_image_urlYes다운로드 가능한 https URL (허용 형식: image/jpeg, image/png) (최대 50MB)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true and openWorldHint=false, so the description earns credit for adding the single-use session constraint and an explicit cost ('호출당 200포인트'), plus the concrete liveness action (turning the head left and right) that determines pass/fail. It stops short of describing the response shape or failure modes, which keeps it from a 5.

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 core purpose is front-loaded in the first clause, but the entire description is duplicated verbatim in English and Korean, roughly doubling length without adding information. The cost note is buried at the end in brackets rather than surfaced earlier.

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 five parameters, a hard dependency on an external session endpoint, and no output schema, the definition should say what a call returns (match score, liveness verdict, rejection reasons) so an agent can interpret results. Session acquisition and cost are covered, but the output contract is left entirely unspecified.

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 description coverage is 100%, so all five parameters (session, threshold, three media URLs with formats and size caps) are already fully documented. The description adds only the provenance of the session token and the implicit link between threshold and face match, which is marginal beyond the schema — baseline 3 applies.

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?

States a specific verb+resource ('Verify identity') and enumerates exactly what is checked: ID screen-capture/editor detection, liveness via head turns, and face match. It also names the required capture session endpoint, so an agent can distinguish it from document_verify or registry_doc_verify without inspecting schemas.

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?

It gives a prerequisite ('Requires a single-use capture session from /rest/kyc_session') which is genuine usage context, but there is no explicit when-to-use/when-not guidance and no routing to the sibling verification tools (document_verify, account_realname) that overlap in the identity-verification space.

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.