Skip to main content
Glama

우리은행 계좌 목록 조회

woori_bank__accounts__list

자격증명이나 로그인 없이 바로 호출할 수 있습니다. 이 호출자가 등록한 우리은행 계좌 연동 목록을 돌려줍니다. 항목마다 거래내역 도구가 쓰는 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": "woori_bank__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.9/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, and the description adds real value beyond them: each call consumes one token, creates an XBOSS task and stores the result, and is explicitly 'not purely read-only' despite reading the institution's data. That disclosure matters because the tool looks like a plain list. It stops short of saying what that stored side effect means for the caller or whether it can be undone.

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 most important fact, that no login is needed, comes first, which is good front-loading. But the middle section drifts across retry semantics, taste mode, and a field that does not exist in this tool's schema, and the sentence that calling again without the key becomes a new request repeats the point already made. It is informative but noticeably longer than the single-parameter surface warrants.

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 one-optional-parameter tool with no output schema, it covers authentication, cost, side effects, return contents, and idempotency behavior, which is close to complete. The gaps are the undefined 'taste' mode limitation and the confusing reference to an institutional idempotency_key field that has no counterpart in the schema.

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

Parameters5/5

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

Schema coverage is 100%, so the baseline would be 3, but the description earns more: it explains the key must be generated and stored before the first logged-in request, reused with identical arguments only when recovering an unanswered request, and regenerated for new executions, and it notes that omitting it makes the call a fresh request. It also warns that the separate institutional idempotency_key field is different and should be left alone, which prevents a plausible mix-up.

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 specific verb and resource: it returns the list of Woori Bank account links registered by the calling user, and it notes that each item carries account_link_id and bank_account_credential_id. The bank name plus the emphasis on the caller's own links distinguishes it from the other banks' accounts__list siblings, though it never explicitly names an alternative tool.

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 usable context: the tool can be called without credentials or login, and in an account-less 'taste' mode the optional field is unavailable. It also explains the retry condition for reusing the idempotency key. However, it never states when an agent should prefer this tool over a sibling accounts list or the login tool, so the guidance is 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