Skip to main content
Glama

IBK 빠른계좌조회 계좌 목록

ibk_fast_account__accounts__list

자격증명이나 로그인 없이 바로 호출할 수 있습니다. 이 호출자가 등록한 IBK기업은행 계좌 연동 목록을 돌려줍니다. 항목마다 잔액 요약 도구가 쓰는 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": "ibk_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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description adds substantial context beyond them: one token is consumed per call, an XBOSS task is created and its result stored, and the call is explicitly not a pure read operation despite querying institution data. The retry semantics for the idempotency key are also spelled out. It loses a point because the actual side effect is described vaguely ('institution data changes follow per-tool execution contents and existing confirmation procedures') rather than concretely.

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 most important facts are front-loaded: no credentials needed, what is returned, and what each item contains, before the idempotency detail. Most sentences earn their place, but the trailing note about institutional idempotency_key fields and the closing sentence about institution data changes are boilerplate-adjacent and slightly dilute the core message.

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 one optional parameter, no output schema, and annotations covering the safety profile, the description supplies enough to call the tool correctly: access requirements, return contents, per-call cost, side effects, and idempotency handling. Minor gaps remain around error behavior, empty-list handling, and pagination, but none block a correct first 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% and the single parameter is optional, so the baseline would be 3, but the description carries meaning the schema explicitly defers to it ('usage is in the tool description'): create and store the key before the first request, reuse the same value only to recover a response-less request, use a fresh value for a new execution, and skip it entirely for unauthenticated trial calls. It also warns that a separate institutional idempotency_key field must be left alone, which prevents a real misuse.

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 states a concrete verb and resource: it returns the list of IBK Industrial Bank account links registered by the calling user, and it names the two fields each item carries (account_link_id, bank_account_credential_id). The bank-specific scope separates it from the hana/kb/nh list siblings, though that differentiation comes mostly from the tool name rather than the prose.

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 usable precondition ('can be called immediately without credentials or login') and a conditional exclusion ('when calling as a trial without an account, this optional field cannot be used'), which is real when-to-use guidance. However, it never states when to prefer this over the sibling list tools or the balance summary tool, nor what to do when no accounts exist, so the guidance stays implied rather than explicit.

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