Skip to main content
Glama

NH농협은행 빠른조회 거래내역

nh_fast_account__transaction_history__search

REQUIRES prior nh_fast_account__session__login call with same account_link_id. 등록된 계좌 하나의 거래내역을 기존 세션으로 조회한다. 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

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "account_link_id": "<account_link_id>"
    },
    "name": "nh_fast_account__transaction_history__search"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateNoEnd date YYYY-MM-DD or YYYYMMDD
sort_orderNoTransaction time sort orderdesc
start_dateNoStart 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_idYesAccount 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. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, and the description earns credit by explaining why: each call creates an XBOSS job and persists its result, so it is explicitly '순수 읽기 전용이 아닙니다', plus token cost per call and per account. It also discloses artifact retention (7 days), a 15-minute download_url, and idempotency-key recovery semantics. It is docked for stuffing in anonymous recovery_receipt boilerplate that conflicts with the stated session-login requirement, muddying which behaviors actually apply.

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 front-loaded, but the body sprawls across roughly twenty sentences mixing session requirements, artifact retention, recovery receipts, idempotency, token accounting, and XBOSS job disclosure. Large blocks (anonymous recovery_receipt, 'losing it cannot be repaired by signing up') appear to be pasted boilerplate with no bearing on a session-authenticated bank transaction lookup, violating the 'every sentence earns its place' test.

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 10 parameters, no output schema, and readOnlyHint=false, the description does cover output mechanics (artifacts[], download_url, retention, job-result recovery) and side effects. However, it never describes what the transaction rows themselves contain or how they are paginated/bounded by start_date and end_date, and the irrelevant anonymous-access text leaves the agent unsure what applies.

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 description coverage is 100%, so the baseline is 3; the description adds real value by spelling out the idempotency-key lifecycle (generate before first request, reuse only to recover a lost response, not available to anonymous calls, distinct from provider idempotency_key) which the schema only gestures at with 'see the tool description'. It also restates the per-account token cost that the schema mentions only briefly.

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 '등록된 계좌 하나의 거래내역을 기존 세션으로 조회한다' names a specific verb (조회/retrieve) and resource (거래내역/transaction history) scoped to a registered account. The preceding line front-loads the prerequisite session call. It loses a point because '하나의 계좌' (one account) contradicts the documented bank_account_credential_ids / all_accounts multi-account modes, and no sibling bank or nh_fast_account__balance__query is named for differentiation.

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 (prior nh_fast_account__session__login with the same account_link_id), along with the exactly-one-of rule across bank_account_credential_id / bank_account_credential_ids / all_accounts, when to request xlsx artifacts, and the recovery path via xdata__job__result for expired links. What is missing is any when-not-to-use guidance or routing to alternatives such as the balance tool or another bank's equivalent.

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