Skip to main content
Glama

KB국민은행 빠른계좌조회 계좌 목록

kb_fast_account__accounts__list

자격증명이나 로그인 없이 바로 호출할 수 있습니다. 이 호출자가 등록한 KB국민은행 계좌 연동 목록을 돌려줍니다. 항목마다 거래내역 도구가 쓰는 account_link_id 와 bank_account_credential_id 가 있습니다. 로그인한 호출이면 첫 요청 전에 request_idempotency_key 값을 만들어 저장하세요. 응답을 받지 못한 그 요청을 되찾을 때만 같은 인자와 함께 그 값을 다시 보내고, 새로 실행할 때는 새 값을 쓰세요. 이 값 없이 다시 부르면 새 요청이 됩니다. 계정 없이 맛보기로 부를 때는 이 선택 칸을 쓸 수 없습니다. 기관 업무에 따로 있는 idempotency_key 칸은 다른 칸이니 그대로 두세요. 호출마다 토큰 1소진 요청 처리 시 XBOSS 작업을 생성하고 처리 결과를 저장합니다. 기관 원본의 조회 여부와 별개로 이 호출은 순수 읽기 전용이 아닙니다. 기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "kb_fast_account__accounts__list"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idempotency_keyNo로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / request_idempotency_key / description
      Previous value: -"Optional same-request recovery key for authenticated calls; see the tool description."New value: +"로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag readOnlyHint=false, and the description justifies that: every call consumes one token, creates an XBOSS job, and persists the result, so the tool is explicitly "순수 읽기 전용이 아닙니다." It also spells out idempotency recovery semantics (reuse the key only to reclaim an unanswered request; a new key for a new execution). What it does not clarify is what the anonymous path actually returns, and the closing sentence about 기관 데이터 변경 is generic boilerplate.

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?

It is front-loaded correctly, leading with the no-login fact and what is returned. But three of the sentences are operational boilerplate (XBOSS job creation, token accounting, the generic 기관 데이터 변경 disclaimer) and the idempotency explanation is dense and repetitive, diluting an otherwise simple one-parameter list call.

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?

For a zero-required-parameter list tool with no output schema, it covers auth, side effects, cost, idempotency, and even the identifier fields returned in each item. The remaining gap is what an anonymous 'taste' call returns given that the idempotency field is unavailable — a caller cannot predict the anonymous response shape.

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 baseline 3 applies — but the schema's own description defers to the tool description for usage ("쓰는 법은 도구 설명에 있습니다"), and the description genuinely delivers: mint-and-store before the first request, reuse only for recovery of an unanswered request, new value otherwise, and unavailable for unauthenticated calls. It also warns that the institution-level idempotency_key is a different field and must be left alone.

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?

"이 호출자가 등록한 KB국민은행 계좌 연동 목록을 돌려줍니다" gives a specific verb (returns a list) and resource (the caller's registered KB account links), and it further pins the shape by naming account_link_id and bank_account_credential_id as the fields the transaction-history tool consumes. That distinguishes it from the sibling transaction_history__search, which the description explicitly references.

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 entry condition (no credentials or login required) and explains the split between logged-in calls and anonymous "맛보기" calls, including that the optional field is unusable anonymously. The implicit routing — use this to obtain the IDs the transaction-history tool needs — is clear but never stated as an explicit 'use this instead of X when Y' rule.

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.

Resources