Skip to main content
Glama

하나은행 빠른계좌조회 계좌 목록

hana_fast_account__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": "hana_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.3/5.0
Behavior5/5

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

The annotations declare readOnlyHint=false with no destructive hint, and the description adds real context beyond them: each call consumes one token, it creates an XBOSS job and persists the processing result, and it explicitly warns that the call is not purely read-only even though the underlying institution lookup is. It also spells out retry/idempotency semantics and the guest-mode restriction, which an agent could not infer from the annotations.

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 purpose statement is front-loaded and clear, but the body is dense and mixes several concerns (idempotency, guest restriction, field disambiguation, token cost, job creation) without visual separation. Some sentences restate the same idea, e.g. the explicit note that calling again without the key becomes a new request repeats the preceding sentence.

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 no output schema, the description carries the return-value burden and does so by naming the two key fields each item contains, which is exactly what a downstream transaction-history call needs. Combined with auth, cost, side-effect, and idempotency disclosure, it is nearly complete for a simple list tool; ordering, empty-result behavior, and pagination are left unstated.

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 schema itself defers usage to the description ('쓰는 법은 도구 설명에 있습니다'). The description earns the higher score by explaining that the key must be generated and stored before the first request, reused only to recover an unanswered request, and replaced for a genuinely new execution, and by warning not to confuse it with the institution's separate idempotency_key field.

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 Hana Bank account links registered by the calling user, and it names the two identifiers each item carries. It implicitly differentiates itself from the transaction-history sibling by noting that sibling consumes account_link_id, but it never names that sibling or any alternative explicitly, so it falls short of a 5.

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 clearly states the tool can be invoked with no credentials or login, and it carves out the guest/trial case where the optional key cannot be used. The idempotency guidance also states precisely when to resend the key (only to recover an unanswered request) versus when to use a fresh value. It does not, however, give broader when-to-use guidance against other list tools.

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