XBOSS

KB국민카드 승인내역 결과 수집

kb_biz_card__approvals__result

Read-only

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

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, yet the description still adds substantial operational context: download_url validity of 15 minutes, 7-day file retention, idempotency-key recovery semantics, and a per-call token cost. Much of the anonymous recovery_receipt material reads as pack-wide boilerplate rather than specific to this authenticated tool, which keeps it from a 5.

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 first two sentences are well front-loaded, but the body becomes a dense run-on covering receipts, link expiry, idempotency, and token cost in long unbroken sentences. Large portions (recovery_receipt rules, anonymous access policy) are irrelevant to an authenticated card-approval call and dilute the actionable content; the trailing Korean cost fragment is attached with no structure.

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?

With no output schema and 8 well-documented parameters, the description covers what an agent needs: the auth prerequisite, artifact lifecycle, and idempotency contract. The remaining gap is workflow placement — it never states that an init/search job must precede it or how max_pages bounds collection.

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, and the description earns above baseline by explaining the account_link_id/session coupling, the request_idempotency_key reuse rules (including that a new key means a new execution), and the conditional xlsx emission tied to output_formats. It does not clarify max_pages behavior, leaving the one non-obvious numeric parameter unexplained.

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 names a specific verb and resource: "Collect KB Biz Card approvals result rows," and adds a concrete output mode (xlsx artifacts in artifacts[]). It does not, however, distinguish itself from the closely named siblings kb_biz_card__approvals__init, __page, and __search, so an agent must infer that this is the terminal collection step.

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?

"REQUIRES prior kb_biz_card__session__login call with same account_link_id" is a genuinely useful prerequisite, and it names xdata__job__result as the fallback for expired links. But the central routing question — when to call this versus approvals__init/__page/__search in the same family — is never addressed.

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?