Skip to main content
Glama

KB국민카드 매입내역 페이지 조회

kb_biz_card__purchases__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__purchases__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

A4.4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false) it discloses real side effects: 1 token consumed per call, an XBOSS task created and its result stored, and an explicit warning that the call '순수 읽기 전용이 아닙니다'. That is substantive. The closing sentence ('기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다') is vague boilerplate that does not actually tell the agent what is mutated, which keeps this from 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.

Conciseness3/5

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

The prerequisite and pagination purpose are front-loaded, which is good, but the middle is dense prose mixing idempotency rules, guest-mode limits, token cost, and task creation. The final two sentences about institutional originals and per-tool confirmation procedures are generic filler that dilutes the actionable parts.

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 paginated read-back tool with no output schema, it covers prerequisites, the search_context round-trip, cost, and non-read-only side effects — the things an agent must know before calling. The one gap is that it never describes what a page response contains (item shape, whether a next-page indicator is returned), forcing the agent to infer from calls to purchases__search.

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 baseline would be 3, but the description carries the operational semantics of request_idempotency_key that the schema deliberately defers to it ('쓰는 법은 도구 설명에 있습니다') — when to create it, when to replay the same value, and that omitting it means a new request. It also resolves a naming hazard by warning that the institutional idempotency_key is a different field.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb+resource in '매입내역의 다른 쪽을 조회합니다' and pins down the mechanism (search_context plus page number). It also names the prerequisite sibling, kb_biz_card__session__login, so an agent can distinguish this page-fetch from the preceding purchases__search without opening either schema.

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

Usage Guidelines5/5

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

It states the ordering rule explicitly ('먼저 호출할 도구: kb_biz_card__session__login (같은 account_link_id)') and the condition for reuse versus fresh execution with the idempotency key. It even gives a negative condition — the field cannot be used in the no-account taster mode — which is the kind of when-not guidance most definitions omit.

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