Skip to main content
Glama

KB국민카드 매입내역 초기화

kb_biz_card__purchases__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__purchases__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.7/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that each call consumes one token, that an XBOSS task is created and its result stored, and that the call is not purely read-only despite the underlying lookup — this is consistent with readOnlyHint=false, not a contradiction. The idempotency semantics (new key = new execution; reuse = recover same request; provider-specific idempotency_key is a different field) are genuinely useful. The paragraph is diluted by generic boilerplate about 기관 데이터 변경 and a confused phrase about 'anonymous taste calls'.

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 most important fact, the login prerequisite, is front-loaded, which is good. But the remainder is a single long run-on passage that mixes idempotency policy, token accounting, internal XBOSS mechanics, and generic compliance boilerplate, some of which does not help an agent decide or call correctly.

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?

With no output schema, the description does the necessary work of naming what comes back (department and card options plus default_search_params). What is missing is how those outputs feed the next step in the purchases flow, which would complete the picture for a four-parameter init tool.

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 coverage is already 100%, so the baseline is 3; the description adds real meaning on top for request_idempotency_key by spelling out its lifecycle and its distinction from a provider-level key. date_from/date_to and account_link_id are left entirely to the schema, which is acceptable given its completeness.

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 action and resource: it prepares 매입내역 (purchase history) lookup and returns selectable departments, card lists, and default_search_params. That is concrete enough for an agent to know what the call produces. It does not contrast itself with siblings such as purchases__search, purchases__page, or purchases__result, so the boundary of 'init' versus those steps is left implicit.

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?

A hard prerequisite is stated up front (prior kb_biz_card__session__login with the same account_link_id), and the idempotency key has explicit reuse rules: reuse only to recover after a lost response, otherwise mint a new key. However, there is no guidance on when to pick this tool over the sibling page/search/result tools, so the ordering of the workflow must be inferred from the name and returned fields.

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