Skip to main content
Glama

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

nh_fast_account__balance__query

REQUIRES prior nh_fast_account__session__login call with same account_link_id. 등록된 NH농협은행 계좌 하나의 현재 잔액을 기존 세션으로 조회합니다. 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_idYes연동 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.5/5.0
Behavior3/5

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

The description adds real value beyond the annotations: it discloses per-account token consumption, that an XBOSS work item is created and its result stored, and the idempotency key recovery semantics. Critically, it says '이 호출은 순수 읽기 전용이 아닙니다', which is consistent with readOnlyHint=false and explains why. However it contradicts itself on cost ('계좌마다 사용 토큰이 하나씩' vs '호출마다 토큰 1소진') and includes confusing asides ('anonymous taste calls', the 기업정보 브리프 analogy) that weaken trust in the disclosure.

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 is correctly placed first, but the body mixes Korean and English, repeats the selection rule that already appears three times in the schema, and pads with off-topic material (a company-info brief comparison, 'anonymous taste calls'). Several sentences do not earn their place and reduce signal.

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?

For a balance query with no output schema, the description never says what comes back (amount, currency, timestamp, per-account shape under all_accounts), which is the main missing piece. It covers prerequisites, cost, and side effects well, but the self-contradictory token accounting leaves the cost model ambiguous for multi-account calls.

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 coverage is 100%, so all five parameters are already documented in structured data, including the exact-one-of selection rule which the description merely repeats. The one piece of genuine added meaning is the idempotency guidance (generate before first request, reuse only to recover a lost response, new key per execution, provider idempotency_key is a different field), which the schema explicitly defers to 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 Korean sentence '등록된 NH농협은행 계좌 하나의 현재 잔액을 기존 세션으로 조회합니다' gives a specific verb (조회), resource (계좌 잔액) and scope (one registered account), which distinguishes it from accounts__list and transaction_history__search. It stops short of naming a sibling alternative, and the surrounding English boilerplate dilutes the front-loaded statement.

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?

The prerequisite is stated unambiguously: a prior nh_fast_account__session__login call with the same account_link_id is required. The mutually exclusive selection rule (exactly one of bank_account_credential_id / bank_account_credential_ids / all_accounts) effectively tells the caller which mode to pick, though it doesn't contrast this tool against sibling query tools.

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