Skip to main content
Glama

KB국민카드 매입내역 검색

kb_biz_card__purchases__search

먼저 호출할 도구: kb_biz_card__session__login (같은 account_link_id). 기간(date_from, date_to)의 매입내역 한 쪽을 조회합니다. 결과에 쪽 정보(pagination)와 다른 쪽을 읽을 때 쓰는 search_context 가 들어 있습니다. 로그인한 호출이면 첫 요청 전에 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": {
      "date_from": "<date_from>",
      "date_to": "<date_to>"
    },
    "name": "kb_biz_card__purchases__search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo선택 입력. 쪽 번호. 기본 1.
date_toYes조회 종료일 YYYY-MM-DD 또는 YYYYMMDD.
date_fromYes조회 시작일 YYYY-MM-DD 또는 YYYYMMDD.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
department_nameNo선택 입력. 부서 이름. 부서 선택 도구가 돌려준 값을 입력해 주세요.
department_sequence_noNo선택 입력. 부서 일련번호. 부서 선택 도구가 돌려준 값을 입력해 주세요.
request_idempotency_keyNo로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / date_from / description
      Previous value: -"Start date YYYY-MM-DD or YYYYMMDD"New value: +"조회 시작일 YYYY-MM-DD 또는 YYYYMMDD."
    • changedInput schema / properties / date_to / description
      Previous value: -"End date YYYY-MM-DD or YYYYMMDD"New value: +"조회 종료일 YYYY-MM-DD 또는 YYYYMMDD."
    • changedInput schema / properties / department_name / description
      Previous value: -"Department name"New value: +"선택 입력. 부서 이름. 부서 선택 도구가 돌려준 값을 입력해 주세요."
    • changedInput schema / properties / department_sequence_no / description
      Previous value: -"Department sequence number"New value: +"선택 입력. 부서 일련번호. 부서 선택 도구가 돌려준 값을 입력해 주세요."
    • changedInput schema / properties / page / description
      Previous value: -"Page number; default 1"New value: +"선택 입력. 쪽 번호. 기본 1."
  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
Behavior3/5

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

Adds real behavior beyond the annotations: every call consumes one token, creates an XBOSS job and persists its result, and explicitly warns that despite being a query it is not purely read-only — consistent with readOnlyHint=false. The closing sentence about institutional data changes following each tool's own confirmation procedure is boilerplate, and the mention of a separate institution-level idempotency_key field that is not in the schema adds mild confusion.

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?

Front-loads the prerequisite tool, then the purpose, then the idempotency mechanics — a sensible order with no filler sentences in the core. The tail-end institutional boilerplate and the stray idempotency_key aside are the only parts that do not earn their place.

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 7-parameter tool with no output schema, it covers the essentials: precondition login, what the response contains (pagination, search_context), cost per call, and retry semantics. It leaves the department filter parameters entirely to the schema and introduces a cross-reference to a field not present in the input schema.

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 baseline is 3. The description does add genuine guidance for request_idempotency_key (the schema itself defers usage to the description) and ties account_link_id to the login step, but it adds nothing about page, department_name, or department_sequence_no beyond what the schema already documents.

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 a specific verb and resource: it retrieves one page (한 쪽) of 매입내역 for a date range, and notes the result carries pagination info and a search_context for reading further pages. That implicitly separates it from the sibling page/result tools, though it never names an alternative search tool (e.g. payments__search or approvals__search) to distinguish the resource domain.

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?

Gives an explicit prerequisite — call kb_biz_card__session__login first with the same account_link_id — plus a precise rule for when to reuse request_idempotency_key (only to recover a request whose response was lost) versus when to generate a new one. It also states an exclusion: the optional idempotency field cannot be used for account-less trial calls.

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