Skip to main content
Glama

KB국민카드 승인내역 페이지 조회

kb_biz_card__approvals__page

먼저 호출할 도구: kb_biz_card__session__login (같은 account_link_id). 앞선 검색이 돌려준 search_context 와 쪽 번호(page)로 승인내역의 다른 쪽을 조회합니다. 로그인한 호출이면 첫 요청 전에 request_idempotency_key 값을 만들어 저장하세요. 응답을 받지 못한 그 요청을 되찾을 때만 같은 인자와 함께 그 값을 다시 보내고, 새로 실행할 때는 새 값을 쓰세요. 이 값 없이 다시 부르면 새 요청이 됩니다. 계정 없이 맛보기로 부를 때는 이 선택 칸을 쓸 수 없습니다. 기관 업무에 따로 있는 idempotency_key 칸은 다른 칸이니 그대로 두세요. 호출마다 토큰 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": {
      "search_context": "<search_context>",
      "page": "<page>"
    },
    "name": "kb_biz_card__approvals__page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYes가져올 쪽 번호. 1 부터 시작합니다.
search_contextYes앞선 검색이 돌려준 search_context 를 그대로 입력해 주세요.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
request_idempotency_keyNo로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / page / description
      Previous value: -"Page number to fetch"New value: +"가져올 쪽 번호. 1 부터 시작합니다."
    • changedInput schema / properties / search_context / description
      Previous value: -"Search context returned by init/search"New value: +"앞선 검색이 돌려준 search_context 를 그대로 입력해 주세요."
  2. 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: +"로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다."
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, and the description explains why and what that means in practice: each call consumes one token, creates an XBOSS task, and stores the result, so the call is not purely read-only even though the institution-side data is only read. That is real added value beyond the annotation flags. The closing sentence about institution data changes following per-tool procedures is generic boilerplate that does not apply to a paging read.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The prerequisite is front-loaded and each paragraph carries operational information an agent needs (prerequisite, paging semantics, idempotency rules, cost, side effects). There is some redundancy, notably restating that calling without the key counts as a new request, plus a boilerplate final sentence. Still compact for the amount of guidance packed in.

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?

Prerequisite, cost, side effects, and idempotency behavior are all covered, which is a lot for a 4-parameter tool with no output schema. However, for a pagination tool it never says how to tell whether more pages exist or what the response contains (e.g., whether a next-page indicator or updated search_context comes back), leaving the paging loop underspecified.

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 100%, so the baseline is 3, but the description goes further by explaining the relationship between search_context (must be the value returned by the preceding search), page (the other side of the same result set), and the login call's account_link_id. The idempotency key guidance — create and store once, reuse only to recover a response-less request, use a fresh value for a new execution — meaningfully exceeds the schema's terse note.

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 gives a specific verb and resource: it fetches another page of approval history (승인내역의 다른 쪽) using the search_context returned by a prior search plus a page number. That distinguishes it from the init/result/search siblings in the approvals family. It never names the specific search tool that produces search_context, so the boundary with kb_biz_card__approvals__search is implied rather than stated.

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?

It clearly states the prerequisite (call kb_biz_card__session__login first with the same account_link_id) and the situation this tool is for (paging past the first result set). It also gives explicit when-not guidance for request_idempotency_key — unusable on an accountless trial call, must not be conflated with the institution's own idempotency_key field. Only the missing piece is which search tool to run before this one.

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