XBOSS

KB국민카드 매입내역 결과 수집

kb_biz_card__purchases__result

Read-only

REQUIRES prior kb_biz_card__session__login call with same account_link_id. Collect KB Biz Card purchases result rows. Files: a document generated from this result, as Excel (xlsx) only when requested in output_formats, listed in artifacts[] of the result with a download_url that works for 15 minutes; each file is kept for 7 days. If a link has expired, call xdata__job__result with the job_id from the result for fresh links. For an anonymous result, keep its private recovery_receipt and send it with the original job_id or pack_run_id to xdata__job__result. It grants access to that result only, until the original file retention expires. Do not publish it. Losing it cannot be repaired by signing up. The receipt also works if the client later signs in; it does not grant access to other results. Without a receipt, results require the original account and lane. 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
`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
`output_formats`	No	Optional. Also return this result as a file (Excel (xlsx)) in artifacts[] of the result. Omit it for data only.
`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"
+}

Changed1 schema field changedOct 9, 2026

addedInput schema / properties / output_formats

Added value: +{
+  "description": "Optional. Also return this result as a file (Excel (xlsx)) in artifacts[] of the result. Omit it for data only.",
+  "items": {
+    "enum": [
+      "xlsx"
+    ],
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array",
+  "uniqueItems": true
+}

First observedSep 22, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the read-only, non-destructive profile, and the description goes well beyond them: 15-minute download_url lifetime, 7-day file retention, artifact placement in artifacts[], per-call token consumption, and detailed idempotency-key recovery semantics. The anonymous/recovery_receipt and 'taste calls' passages read as generic template boilerplate that is largely irrelevant to an authenticated card-purchases tool, slightly muddying rather than contradicting the behavior.

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 is correctly front-loaded, but the body is a run-on block that mixes file retention, receipt recovery, idempotency policy, and token cost without paragraphing. The anonymous-receipt and 'taste calls' material is boilerplate that does not belong in a description for a logged-in KB card tool and dilutes the actionable content.

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 an 8-parameter tool with no output schema, the description does substantial work explaining the return shape (artifacts[], download_url, retention) and the recovery path for expired links. The notable omission is the relationship to purchases__init/page — an agent can infer from 'result rows' but is never told the job must be initiated first or how page collection interacts with this call.

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 earns credit by explaining what output_formats actually triggers (an Excel file in artifacts[] with a 15-minute link, not just a flag) and by carrying the full meaning of request_idempotency_key, which the schema explicitly defers to the tool description. Date filters, max_pages, and department fields are left entirely to the schema.

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 — 'Collect KB Biz Card purchases result rows' — which pins down the action and the domain. It does not, however, distinguish itself from the adjacent kb_biz_card__purchases__init/page/search tools, and it never states the critical fact that a purchases job must be started before this can collect anything.

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?

Gives an explicit prerequisite ('REQUIRES prior kb_biz_card__session__login call with same account_link_id') and routes the agent elsewhere on failure ('If a link has expired, call xdata__job__result with the job_id'). It also explains when to supply output_formats and how to reuse request_idempotency_key. It gives no guidance on when to prefer this over purchases__page or purchases__search, which is the main sibling ambiguity.

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?