Skip to main content
Glama

1원 인증

transfer_1won

Send a 1 KRW verification deposit to a Korean bank account and return the 4-character verification code printed on the transaction. 대한민국 은행 계좌로 1원을 입금해 적요에 표시되는 인증코드를 반환합니다. 계좌 실소유 확인(1원 인증) 절차에 사용합니다. bank_code 또는 bank_name 중 하나는 입력해야 합니다. 입금통장메모는 자동 생성되며 응답의 입금통장메모 값으로 인증합니다. 응답을 받지 못해 다시 호출할 때는 같은 idempotency_key 를 넣으면 1원을 다시 보내지 않고 처음 결과를 요금 없이 돌려줍니다. [호출당 60포인트]

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": {
      "account_num": "<account_num>"
    },
    "name": "transfer_1won"
  }
}

Input Schema

NameRequiredDescriptionDefault
bank_codeNo은행 코드 (bank_code Tool로 조회 가능, 예: 004)
bank_nameNo은행명 (예: 국민). bank_code 대신 입력 가능
account_numYes계좌번호 (숫자만, 하이픈 제외)
idempotency_keyNo같은 송금을 두 번 하지 않게 하는 요청 키(영문·숫자와 - _ . :, 1~80자). 인증 1건마다 새 값, 재시도 때는 같은 값

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / idempotency_key
      Added value: +{
      +  "description": "같은 송금을 두 번 하지 않게 하는 요청 키(영문·숫자와 - _ . :, 1~80자). 인증 1건마다 새 값, 재시도 때는 같은 값",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations it discloses cost (60 points per call), that the deposit memo is auto-generated and is the value to verify against, and precise retry semantics: resending with the same idempotency_key returns the original result without re-sending the 1 KRW and without charge. These are exactly the operational facts an agent needs for a money-moving, open-world call that the annotations alone (readOnlyHint=false, openWorldHint=true, destructiveHint=false) cannot convey.

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 content is front-loaded with the action and the returned value, then layered with constraints, retry behavior, and cost in a sensible order. The English and Korean sentences partially mirror each other, which adds some redundancy, but the Korean text carries additional facts (one-of bank identifier, memo verification, idempotency, pricing) rather than pure duplication.

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

Completeness5/5

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

There is no output schema, and the description compensates by specifying what comes back (a 4-character code plus the deposit memo to match). For a 4-parameter, money-moving, open-world tool it also covers cost, retry safety, and the bank-identifier requirement, leaving no material gap before invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds a cross-parameter rule the schema does not express: exactly one of bank_code or bank_name must be provided (the schema only marks account_num required). It also reinforces idempotency_key usage on retries, though it adds no format detail beyond the schema.

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 names a specific verb and resource — sending a 1 KRW verification deposit to a Korean bank account — and states the return value (the 4-character verification code printed on the transaction). It also names the workflow it belongs to (account real-ownership verification), which distinguishes it cleanly from the sibling bank_code lookup and account_realname 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 states the context of use ('계좌 실소유 확인(1원 인증) 절차에 사용합니다') and adds a call-level constraint that bank_code or bank_name must be supplied. It does not explicitly say when NOT to use it or name an alternative for other verification flows, so it stops short of full when/when-not routing.

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.