Skip to main content
Glama

KB국민카드 결제내역 초기화

kb_biz_card__payments__init

REQUIRES prior kb_biz_card__session__login call with same account_link_id. 결제내역 조회를 준비합니다. 고를 수 있는 부서 목록과 검색에 쓸 기본값(default_search_params)을 돌려줍니다. 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

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": "kb_biz_card__payments__init"
  }
}

Input Schema

NameRequiredDescriptionDefault
date_toNoEnd date YYYY-MM-DD or YYYYMMDD
date_fromNoStart date YYYY-MM-DD or YYYYMMDD
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, and the description goes well beyond them: it discloses a per-call token cost ("호출마다 토큰 1소진"), that an XBOSS task is created and its result stored, and explicitly warns that the call is not purely read-only despite reading from the institution source — consistent with readOnlyHint=false. What "XBOSS 작업" concretely means remains opaque, keeping this below a 5.

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 correctly front-loaded, but the body is bloated and mixes Korean and English mid-paragraph, and the idempotency block drags in boilerplate that does not apply here ("This optional key is not available to anonymous taste calls"). Several sentences could be cut without losing information an agent needs to call this tool.

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?

There is no output schema, but the description compensates by naming the returned department list and default_search_params, and it covers auth prerequisite, token cost, and idempotency behavior. What is missing is the downstream step (which tool consumes default_search_params), so an agent knows how to start but not how to continue.

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 100%, so the schema already documents date_from, date_to, account_link_id, and the key. The description still adds real meaning: it requires the same account_link_id as the login, and it spells out idempotency semantics (generate and save before the first request, reuse only to recover a lost response, new key for a new execution, no key means a new request, provider-specific idempotency_key is a different field). That is meaningful guidance beyond the schema text.

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 that the call prepares a payment-history lookup ("결제내역 조회를 준비합니다") and concretely names what it returns: the selectable department list and default_search_params. That is more than a restatement of the title. It stops short of naming the sibling it feeds (payments__search/page/result), so the agent must infer the init-then-search chain from the name alone.

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?

The prerequisite is explicit: a prior kb_biz_card__session__login call with the same account_link_id is REQUIRED. Usage is otherwise only implied by "조회를 준비합니다" — there is no statement that this should precede payments__search or payments__page, and no when-not guidance. Adequate but with a clear routing gap given five sibling payment 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