Skip to main content
Glama

KB국민카드 결제내역 페이지 조회

kb_biz_card__payments__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__payments__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.7/5.0
Behavior4/5

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

Annotations already flag readOnlyHint=false and destructiveHint=false, and the description reinforces rather than contradicts them, explicitly warning that the call is not purely read-only despite querying institution data. It adds real operational context: 1 token consumed per call, an XBOSS task created and its result stored, and the idempotency replay protocol. The remaining gap is what the response looks like after a replay versus a fresh request.

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 sentences are dense and mix several concerns (prerequisite routing, idempotency protocol, token cost, XBOSS task creation, read-only caveats) without clear separation. The purpose statement is buried behind the prerequisite sentence. The note that the institution-level idempotency_key field is a different field adds confusion because no such field appears in this schema.

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?

For a paginated tool with no output schema, the description explains how to continue paging by consuming search_context and page, but it never says how an agent learns whether more pages exist or what a page response contains. It covers safety and cost well. Paging termination is the missing piece.

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 description coverage is 100%, so the baseline is 3, and the schema already documents page, search_context, and account_link_id. The description adds genuine meaning for request_idempotency_key (create before first request, resend only to recover an unanswered request, use a new value for new executions) and for guest-call restrictions, which the schema explicitly defers to it. That pushes it just above baseline.

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 second sentence states a specific verb and resource: retrieve another page of payment history using the search_context and page number returned by a prior search. That distinguishes it from payments__search/init/result siblings. It loses a point only because the purpose is preceded by a prerequisite instruction rather than front-loaded.

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 names the prerequisite tool (kb_biz_card__session__login with the same account_link_id) and the condition for use (a prior search returned search_context). It also rules out the idempotency field for guest/trial calls. There is no explicit exclusion of the first-page case, though 'another page' implies it.

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