Skip to main content
Glama

IBK 빠른계좌조회 잔액 요약

ibk_fast_account__accounts__quick_summary__get

REQUIRES prior ibk_fast_account__session__login call with same account_link_id. 등록된 IBK기업은행 계좌 하나의 잔액과 당일 요약을 조회합니다. Files: a document generated from this result, as Excel (xlsx) only when requested in output_formats, listed in artifacts[] of the result with a download_url that works for 15 minutes; each file is kept for 7 days. If a link has expired, call xdata__job__result with the job_id from the result for fresh links. For an anonymous result, keep its private recovery_receipt and send it with the original job_id or pack_run_id to xdata__job__result. It grants access to that result only, until the original file retention expires. Do not publish it. Losing it cannot be repaired by signing up. The receipt also works if the client later signs in; it does not grant access to other results. Without a receipt, results require the original account and lane. Send exactly one of bank_account_credential_id (one account), bank_account_credential_ids (several accounts) or all_accounts (every account). 계좌마다 사용 토큰이 하나씩 듭니다. 기업정보 브리프처럼 한 번에 여러 사용 토큰을 쓰는 업무는 그 값만큼 계좌마다 듭니다. For an authenticated call, generate and save request_idempotency_key before the first request. Reuse it with the same arguments only to recover that request after a lost response; use a new key for a new execution. Without it, calling again remains a new request. This optional key is not available to anonymous taste calls. Keep any provider-specific idempotency_key unchanged; it is a different field. 호출마다 토큰 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__quick_summary__get"
  }
}

Input Schema

NameRequiredDescriptionDefault
all_accountsNoSet to true to run this once for every account registered for this bank. Each account is handled separately and uses the tokens this action costs. Send exactly one of bank_account_credential_id (one account), bank_account_credential_ids (several accounts) or all_accounts (every account).
output_formatsNo선택 입력입니다. 결과를 엑셀(xlsx) 파일로도 받으려면 입력해 주세요. 파일은 결과의 artifacts[] 에 실립니다. 비워 두면 데이터만 받습니다.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 서비스에 계정을 여러 개 연동했을 때만 직접 입력해 주세요.
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.
bank_account_credential_idNobank_account_credential_id of one registered account - take it from this bank's accounts list tool
bank_account_credential_idsNobank_account_credential_id values from this bank's accounts list tool. Runs this once for each listed account. Each account is handled separately and uses the tokens this action costs. Send exactly one of bank_account_credential_id (one account), bank_account_credential_ids (several accounts) or all_accounts (every account).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only flag readOnlyHint=false with no explanation; the description adds why, stating that the call creates an XBOSS job, stores the result, and '순수 읽기 전용이 아닙니다'. It also discloses token cost per account, 15-minute download_url lifetime, 7-day file retention, and the idempotency-key recovery rule. Some of the receipt and anonymous-access prose appears copied from job/result tools and is not clearly relevant here, which dilutes the signal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The prerequisite is correctly front-loaded, but the body mixes three languages and packs in anonymous recovery_receipt handling, provider-specific idempotency_key caveats, and retention policy prose that reads as generic template text. Large portions do not earn their place for a single-account balance lookup.

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

Completeness3/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 burden of explaining returns; it covers the artifacts[] file behavior and link expiry well but never describes the balance and summary fields the agent will actually receive. Preconditions, token cost, and idempotency are covered, so it is adequate but leaves the core payload shape undocumented.

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 meaning beyond the schema: each account consumes one usage token, and multi-account workloads such as a company-info brief cost that many tokens per account. It also clarifies the exclusive-or relationship among the three account selectors in prose, though the schema already states it.

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 Korean sentence '등록된 IBK기업은행 계좌 하나의 잔액과 당일 요약을 조회합니다' states a specific verb (retrieve) and resource (balance plus same-day summary for one registered IBK account). It is distinguishable from the accounts list tool, which it references as the source of the credential id. The purpose is clear but sits behind a prerequisite sentence and a large block of unrelated boilerplate.

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?

Explicit preconditions are given: a prior ibk_fast_account__session__login with the same account_link_id, and the rule to send exactly one of bank_account_credential_id, bank_account_credential_ids, or all_accounts. It also routes recovery to xdata__job__result when a download link expires. It stops short of stating when to prefer this tool over a full transaction-history or list call for the same account.

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