Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

KB국민은행 빠른계좌조회 거래내역

kb_fast_account__accounts__transaction_history__search
Read-only

REQUIRES prior kb_fast_account__session__login call with same account_link_id. Search transaction history for one registered KB Kookmin Bank fast-account using the existing provider session. 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소진

Input Schema

NameRequiredDescriptionDefault
end_dateYesEnd date YYYY-MM-DD or YYYYMMDD
sort_orderNoTransaction time sort orderdesc
start_dateYesStart date YYYY-MM-DD or YYYYMMDD
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_formatsNoOptional. Also return this result as a file (Excel (xlsx)) in artifacts[] of the result. Omit it for data only.
account_link_idNoAccount link ID (UUID v4). Optional — the server auto-resolves from your API key when omitted. Provide explicitly only when you have multiple connections for the same provider.
transaction_typeNoTransaction direction sent to the bank; the server does not filter the returned rowsall
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. Changed1 schema field changed
    • addedInput schema / properties / request_idempotency_key
      Added value: +{
+  "description": "Optional same-request recovery key for authenticated calls; see the tool description.",
+  "maxLength": 128,
+  "minLength": 1,
+  "pattern": "^[\\x20-\\x7E]+$",
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • changedInput schema / properties / account_link_id / description
      Previous value: -"Account link ID (UUID v4). Optional — the server auto-resolves from your API key when omitted. Provide explicitly only when you have multiple certificates for the same provider. Each institution has a separate ID (Hometax != NHIS != NPS != FourInsure)."New value: +"Account link ID (UUID v4). Optional — the server auto-resolves from your API key when omitted. Provide explicitly only when you have multiple connections for the same provider."
    • changedInput schema / properties / transaction_type / description
      Previous value: -"Transaction direction filter"New value: +"Transaction direction sent to the bank; the server does not filter the returned rows"
  3. Changed3 schema fields changed
    • addedInput schema / properties / all_accounts
      Added value: +{
+  "description": "Set 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).",
+  "type": "boolean"
+}
    • addedInput schema / properties / bank_account_credential_ids
      Added value: +{
+  "description": "bank_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).",
+  "items": {
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array"
+}
    • changedInput schema / required
      Previous value: -[
-  "bank_account_credential_id",
-  "start_date",
-  "end_date"
-]New value: +[
+  "start_date",
+  "end_date"
+]
  4. Changed1 schema field changed
    • addedInput schema / properties / output_formats
      Added value: +{
+  "description": "Optional. Also return this result as a file (Excel (xlsx)) in artifacts[] of the result. Omit it for data only.",
+  "items": {
+    "enum": [
+      "xlsx"
+    ],
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array",
+  "uniqueItems": true
+}
  5. Changed6 schema fields changed
    • addedInput schema / properties / bank_account_credential_id / description
      Added value: +"bank_account_credential_id of one registered account - take it from this bank's accounts list tool"
    • removedInput schema / properties / bank_account_credential_id / dynamic_options
      Removed value: -{
-  "execution_target": true,
-  "selection_ids_param": "bank_account_credential_ids",
-  "selection_mode_param": "bank_account_selection_mode",
-  "service_key": "kb_fast_account",
-  "source": "credential_bank_accounts"
-}
    • removedInput schema / properties / bank_account_credential_id / user_editable
      Removed value: -false
    • removedInput schema / properties / bank_account_credential_id / visibility
      Removed value: -"system"
    • removedInput schema / properties / bank_account_credential_ids
      Removed value: -{
-  "dynamic_options": {
-    "execution_target": false,
-    "service_key": "kb_fast_account",
-    "source": "credential_bank_accounts"
-  },
-  "items": {
-    "format": "uuid",
-    "type": "string"
-  },
-  "type": "array",
-  "ui_type": "credential_bank_accounts",
-  "visibility": "user"
-}
    • removedInput schema / properties / bank_account_selection_mode
      Removed value: -{
-  "default": "default",
-  "enum": [
-    "selected",
-    "default"
-  ],
-  "type": "string",
-  "ui_type": "select",
-  "visibility": "user"
-}
  6. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare readOnly/non-destructive; the description adds substantial context beyond that — per-account and per-call token consumption, 15-minute download_url lifetime, 7-day file retention, and the anonymous recovery_receipt rules (result-scoped, non-repairable, not transferable). It also explains idempotency-key reuse semantics, which the schema explicitly defers to it.

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 is a loosely spliced wall of text with garbled phrasing ('Files: a document generated from this result, as Excel (xlsx) only when requested'), duplicated token-cost statements in Korean and English, and a long receipt paragraph that buries the core call semantics.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 10 parameters and no output schema, the description carries the return-shape burden and does so — it documents artifacts[] with download_url and its lifetime. Prerequisites, cost, recovery paths, and file retention are all covered; an agent has what it needs to call this correctly in normal and failure cases.

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 most parameters are self-documenting, but the description still contributes: the exactly-one-of rule across bank_account_credential_id / bank_account_credential_ids / all_accounts, the per-account token implication of all_accounts, and the request_idempotency_key lifecycle that the schema points at the description for.

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+resource+scope: search transaction history for one registered KB Kookmin Bank fast-account via an existing provider session. The bank is unambiguous from the name/title, though it never explicitly contrasts itself with the parallel hana_fast_account and shinhan_easy transaction-history siblings.

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 gives a hard prerequisite (prior kb_fast_account__session__login with the same account_link_id) and routes the agent onward for two edge cases: expired links and anonymous results both go to xdata__job__result. It also states the one-of credential selection rule. What it lacks is a 'use this instead when...' against the sibling bank tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All XBOSS toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources