Skip to main content
Glama

KB국민카드 승인내역 초기화

kb_biz_card__approvals__init

먼저 호출할 도구: kb_biz_card__session__login (같은 account_link_id). 승인내역 조회를 준비합니다. 고를 수 있는 부서와 카드 목록, 검색에 쓸 기본값(default_search_params)을 돌려줍니다. 로그인한 호출이면 첫 요청 전에 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": "kb_biz_card__approvals__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_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

A3.6/5.0
Behavior3/5

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

Strong disclosure beyond annotations: 1 token cost per call, creation of an XBOSS task with stored result, and an explicit warning that this call is NOT purely read-only even though the institution source lookup is a read. This is consistent with readOnlyHint=false and destructiveHint=false, not contradictory. However, it never says what the write side effect actually alters or whether re-init overwrites prior state, so the mutation footprint stays vague.

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?

Front-loaded correctly with the call-first instruction and the return contents, which is the right ordering. But the idempotency paragraph runs long, and the closing sentences about XBOSS task creation and institution data changes are generic boilerplate that dilutes the actionable content.

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 describe the return payload (departments, cards, default_search_params), and it covers prerequisite, guest restriction, token cost, and non-read-only behavior. Missing only the handoff to the search/page/result tools and the concrete nature of the stored write.

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 four parameters are already documented, making 3 the baseline. The description does add real value for request_idempotency_key (create and store before the first request, reuse only to recover an unanswered request, new value for a new execution, and a warning not to confuse it with the institution-level idempotency_key field). Date range parameters are not elaborated at all in the description.

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?

States it prepares card-approval-history lookup and specifically what it returns: selectable department and card lists plus default_search_params for search. That distinguishes it from approvals__search/page/result, though those siblings are never named, so an agent must infer the handoff.

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?

Explicit prerequisite: call kb_biz_card__session__login first with the same account_link_id, and an explicit exclusion for guest/no-account calls where the selection fields are unusable. It does not state the next step (feed default_search_params into approvals__search), leaving the follow-on workflow implicit.

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