Skip to main content
Glama

NH농협은행 빠른조회 계좌 목록

nh_fast_account__accounts__list

자격증명이나 로그인 없이 바로 호출할 수 있습니다. 이 호출자가 등록한 NH농협은행 계좌 연동 목록을 돌려줍니다. 항목마다 잔액과 거래내역 도구가 쓰는 account_link_id 와 bank_account_credential_id 가 있습니다. 로그인한 호출이면 첫 요청 전에 request_idempotency_key 값을 만들어 저장하세요. 응답을 받지 못한 그 요청을 되찾을 때만 같은 인자와 함께 그 값을 다시 보내고, 새로 실행할 때는 새 값을 쓰세요. 이 값 없이 다시 부르면 새 요청이 됩니다. 계정 없이 맛보기로 부를 때는 이 선택 칸을 쓸 수 없습니다. 기관 업무에 따로 있는 idempotency_key 칸은 다른 칸이니 그대로 두세요. 호출마다 토큰 1소진 요청 처리 시 XBOSS 작업을 생성하고 처리 결과를 저장합니다. 기관 원본의 조회 여부와 별개로 이 호출은 순수 읽기 전용이 아닙니다. 기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nh_fast_account__accounts__list"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idempotency_keyNo로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / request_idempotency_key / description
      Previous value: -"Optional same-request recovery key for authenticated calls; see the tool description."New value: +"로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다."
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false, openWorldHint=true, destructiveHint=false, and the description adds materially: each call consumes 1 token, request processing creates XBOSS jobs and stores their results, and the call is explicitly not pure read-only despite the underlying institution read. It also spells out the retry contract — reuse request_idempotency_key only to recover an unanswered request, use a fresh value for a new execution, and omitting it means a new request — and warns not to confuse it with the institution-level idempotency_key field.

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?

Purpose is front-loaded, but the body is one long unstructured paragraph mixing linking metadata, idempotency rules, billing cost, job creation, and safety caveats, with some redundancy about re-sending without the key producing a new request. It is readable but would benefit from grouping into purpose / idempotency / side-effects.

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 zero-required-parameter list tool with no output schema, the description covers purpose, the fields an agent will need downstream, the idempotency contract, and the cost/side-effect profile. Minor gaps remain: nothing about ordering, empty-list behavior, or whether the linked list is scoped per credential.

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

Parameters5/5

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

Schema coverage is already 100%, and the schema description itself defers to the tool description ('쓰는 법은 도구 설명에 있습니다'), which the description honors by defining lifecycle semantics: generate and store before the first authenticated request, resend only with identical arguments to recover a lost response, new value otherwise, and unavailable in anonymous preview mode. This goes well beyond the type/pattern/length constraints in the schema.

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 and resource: it returns the list of NH농협은행 account links registered by the calling user, and notes each item carries balance plus the account_link_id and bank_account_credential_id used by downstream tools. That is concrete and agent-usable, but it does not explicitly contrast itself with the sibling bank account-list tools or with nh_fast_account__balance__query, so differentiation rests on the tool name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the mention that item IDs are what the balance and transaction-history tools consume suggests the natural workflow (list first, then query), and it states the optional field cannot be used in an unauthenticated 'taste' call. There is no explicit statement of when to prefer this over the balance/history siblings, though the no-login calling condition is useful context.

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