Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

KB국민카드 결제내역 초기화

kb_biz_card__payments__init
Read-only

REQUIRES prior kb_biz_card__session__login call with same account_link_id. Initialize KB Biz Card payments inquiry for a date range. 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

NameRequiredDescriptionDefault
date_toNoEnd date YYYY-MM-DD or YYYYMMDD
date_fromNoStart date YYYY-MM-DD or YYYYMMDD
account_link_idNoAccount 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).
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. Changed1 schema field changed
    • removedInput schema / required
      Removed value: -[
-  "date_from",
-  "date_to"
-]
  3. First observed

TDQS

A3.7/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, but the description adds meaningful context beyond them: authentication prerequisite, per-call token consumption, idempotency recovery behavior, and the restriction for anonymous taste calls. There is no contradiction with the annotations.

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?

The description is front-loaded with the login prerequisite and tool purpose, and the idempotency guidance is relevant. It is somewhat verbose and includes a slightly unclear phrase about anonymous taste calls, but most sentences earn their place given the subtle idempotency semantics.

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 complex initialization tool with many sibling payment tools, the description covers authentication and idempotency well but omits the expected next step or how it relates to payments__page, payments__result, and payments__search. With no output schema, it also does not indicate what initialization returns or what the agent should do immediately afterward.

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 would be 3, but the description adds essential meaning for request_idempotency_key beyond the schema's brief note, including when to reuse it versus generate a new one. It also reinforces the account_link_id prerequisite with session login, though date parameters are already fully covered by 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?

The description states a specific verb and resource: initialize a KB Biz Card payments inquiry for a date range. It is clear what the tool does, but it does not explicitly distinguish this initialization step from sibling tools such as kb_biz_card__payments__search or kb_biz_card__payments__page.

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 clearly states the prerequisite of a prior kb_biz_card__session__login call with the same account_link_id and gives detailed idempotency-key reuse rules. However, it does not explicitly tell the agent when to choose this tool instead of payments__search, payments__page, or payments__result, leaving the workflow placement mostly implied by the 'init' name.

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

All XBOSS toolsInspect
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