Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

신한은행 거래내역 조회

shinhan_easy__accounts__transaction_history__search
Read-only

REQUIRES prior shinhan_easy__auth__id_password_session__login call with same account_link_id. Search Shinhan easy-inquiry transaction history for one account. 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
max_pagesNoMaximum pages to fetch; default 20, max 100
sort_orderNoOrder of the returned transactions by date; desc is newest first (default), asc is oldest first.
start_dateYesStart date YYYY-MM-DD or YYYYMMDD
employee_ynNoProvider employee flag; default 2
include_rawNoInclude raw provider response fields
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).
business_typeNoProvider business type; default 2
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.
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.
bank_account_credential_idNoOpaque bank-account credential selected by the user
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. Changed1 schema field 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."
  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. Changed2 schema fields changed
    • removedInput schema / properties / bank_account_credential_id / visibility
      Removed value: -"system"
    • addedInput schema / properties / sort_order / description
      Added value: +"Order of the returned transactions by date; desc is newest first (default), asc is oldest first."
  6. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With readOnlyHint=true already covering safety, the description adds real operational detail: auth prerequisite, 15-minute download_url lifetime, 7-day file retention, the recovery path via xdata__job__result with job_id, recovery_receipt handling, and per-account token consumption. Some of the receipt text is tangential to invoking this tool, but the behavioral burden is clearly met.

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 core purpose is front-loaded in one sentence, but the remainder is a 200+ word wall that drifts from artifacts to recovery receipts to idempotency keys to Korean token notes, with a mid-sentence jump into 'Files:'. Much of it is generic fleet-wide boilerplate that an agent must wade through to reach the account-selection rule.

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 13-parameter read tool with no output schema but with readOnly annotations and complete schema descriptions, the definition covers prerequisites, idempotency, file artifacts and result recovery. Missing only an explicit note on pagination behavior tied to max_pages and how multiple-account results are keyed.

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

Parameters3/5

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

Schema description coverage is 100%, so all 13 parameters are already documented, including the account-selection exclusivity rule and enum for sort_order. The description's main added value is the per-account token cost in Korean; otherwise it restates schema content, so the baseline of 3 applies.

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 third sentence states a specific verb and resource: 'Search Shinhan easy-inquiry transaction history for one account.' That is enough to distinguish it from the sibling session/login and accounts list tools, though the 'for one account' scope is immediately muddied by support for bank_account_credential_ids and all_accounts, and no sibling is named explicitly.

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 states a hard prerequisite ('REQUIRES prior shinhan_easy__auth__id_password_session__login call with same account_link_id') and gives an explicit selection rule ('Send exactly one of bank_account_credential_id, bank_account_credential_ids or all_accounts'), plus when to add output_formats. It lacks any explicit statement of when to pick this over shinhan_easy__accounts__list.

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