XBOSS

KB국민카드 매입내역 검색

kb_biz_card__purchases__search

Read-only

REQUIRES prior kb_biz_card__session__login call with same account_link_id. Search KB Biz Card purchases rows. For an authenticated call, generate and save request_idempotency_key before the first request. Reuse it with the same arguments only to recover that request after a lost response; use a new key for a new execution. Without it, calling again remains a new request. This optional key is not available to anonymous taste calls. Keep any provider-specific idempotency_key unchanged; it is a different field. 호출마다 토큰 1소진

Input Schema

Name	Required	Description
`page`	No	Page number; default 1
`date_to`	Yes	End date YYYY-MM-DD or YYYYMMDD
`date_from`	Yes	Start date YYYY-MM-DD or YYYYMMDD
`max_pages`	No	Maximum pages to collect
`account_link_id`	No	Account link ID (UUID v4). Optional — the server auto-resolves from your API key when omitted. Provide explicitly only when you have multiple certificates for the same provider. Each institution has a separate ID (Hometax != NHIS != NPS != FourInsure).
`department_name`	No	Department name
`department_sequence_no`	No	Department sequence number
`request_idempotency_key`	No	Optional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

addedInput schema / properties / request_idempotency_key

Added value: +{
+  "description": "Optional same-request recovery key for authenticated calls; see the tool description.",
+  "maxLength": 128,
+  "minLength": 1,
+  "pattern": "^[\\x20-\\x7E]+$",
+  "type": "string"
+}

First observedSep 22, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true and destructiveHint=false, and the description adds useful context beyond them: authentication requirements, idempotency key recovery semantics, and token consumption per call. The idempotency guidance is detailed, though the phrase about "anonymous taste calls" is unclear and the reference to a provider-specific idempotency_key field is not represented in the schema.

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 description front-loads the authentication prerequisite and the core search purpose, which is good. However, the long idempotency discussion contains confusing wording and references a field not present in the schema, making it less tight than it could be.

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 search tool with no output schema and pagination-related parameters, the description covers authentication and idempotency but does not explain return behavior, pagination flow, or how this relates to the purchases__init/page/result siblings. It is minimally adequate to invoke the tool but leaves workflow context incomplete.

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 meaningfully expands the semantics of request_idempotency_key, which the schema only delegates with "see the tool description." It does not add much for the date range, pagination, or department parameters, but the tricky idempotency parameter is well covered.

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 states a specific verb and resource: "Search KB Biz Card purchases rows." This is clear enough to understand the operation, but it does not differentiate from sibling tools such as kb_biz_card__purchases__page, kb_biz_card__purchases__result, or kb_biz_card__payments__search.

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

Usage Guidelines3/5

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

It provides a clear prerequisite: a prior kb_biz_card__session__login call with the same account_link_id. However, it does not explain when to use this search tool versus sibling purchases pagination/result tools or the payments search tool, leaving the workflow choice implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All XBOSS tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?