Skip to main content
Glama

NH농협은행 빠른조회 잔액 조회

nh_fast_account__balance__query

REQUIRES prior nh_fast_account__session__login call with same account_link_id. 등록된 계좌 하나의 현재 잔액을 기존 세션으로 조회한다. 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__balance__query"
  }
}

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).
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.
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 declare readOnlyHint=false, and the description corroborates and explains why: '기관 원본의 조회 여부와 별개로 이 호출은 순수 읽기 전용이 아닙니다', plus it creates an XBOSS job and stores the result. It also discloses per-account token consumption ('계좌마다 사용 토큰이 하나씩 듭니다', '호출마다 토큰 1소진'), which annotations do not capture. Minor deduction for the muddy sentence about multi-token '기업정보 브리프' workloads.

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 prerequisite and purpose are front-loaded, but the body is a long mixed Korean/English block that restates the 'send exactly one of' rule already present twice in the schema, and includes a hard-to-parse analogy about token usage. Several sentences could be cut without losing information.

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?

Auth, cost, idempotency and side effects are covered, but with no output schema the description never indicates what a balance result contains (amount, currency, per-account grouping when all_accounts is used). For a multi-account query this leaves a meaningful gap for the caller.

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 the baseline is 3; the schema already spells out the exactly-one-of rule for the three selectors and the meaning of account_link_id. The description adds little beyond repeating the selector rule and tying multi-account selection to multiplied token cost, and its idempotency-key explanation largely duplicates what the schema field description defers to.

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 names a specific verb and resource in Korean ('등록된 계좌 하나의 현재 잔액을 ... 조회한다' – query the current balance of one registered account) and states the session dependency up front. The balance-query purpose is distinguishable from the sibling accounts__list and transaction_history__search by resource, though neither sibling is mentioned by name.

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 concrete precondition ('REQUIRES prior nh_fast_account__session__login call with same account_link_id') and a clear selector rule (exactly one of bank_account_credential_id / bank_account_credential_ids / all_accounts). Idempotency-key usage is also scoped (reuse only to recover a lost response, new key for new execution). It stops short of naming when to prefer this over a sibling tool.

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