XBOSS

KB국민카드 결제내역 결과 수집

kb_biz_card__payments__result

Read-only

REQUIRES prior kb_biz_card__session__login call with same account_link_id. Collect KB Biz Card payments 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.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true/destructiveHint=false, and the description is consistent with them while adding real context: per-call token cost, 15-minute download_url lifetime, 7-day file retention, and detailed idempotency-key semantics (new key per execution, reuse only to recover a lost response). Some of this is boilerplate about anonymous results and recovery receipts that appears irrelevant to an authenticated card-statement pull, which dilutes rather than contradicts.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The requirement is front-loaded well, but the body is a run-on block mixing artifact retention, receipt recovery, publishing warnings, and idempotency rules in no clear hierarchy. Large portions (anonymous recovery_receipt, 'taste calls', publishing warnings) look copy-pasted and do not apply to this tool.

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?

With no output schema, the description should characterize the returned rows, but it only describes the optional artifact. Pagination behavior (max_pages), date-range limits, and the effect of department filters are unexplained, and irrelevant receipt material occupies space that could carry that information.

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; the description earns more by explaining that output_formats produces an xlsx artifact in artifacts[] and by giving operational rules for request_idempotency_key that the schema only points back to. It does not explain max_pages, department_name, or department_sequence_no beyond 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?

"Collect KB Biz Card payments result rows" is a specific verb+resource statement that an agent can act on. However, it never differentiates this tool from its close siblings kb_biz_card__payments__search, __page, and __init, which share the same resource and are distinguished only by the opaque 'result' suffix.

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 gives an explicit precondition (prior kb_biz_card__session__login with the same account_link_id) and a clear alternative for expired links (xdata__job__result with job_id). But it never says when to call this versus payments__search or payments__page, or what stage of the pipeline this terminates, so pipeline placement is only implied.

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?