Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

KB국민카드 승인내역 초기화

kb_biz_card__approvals__init
Read-only

REQUIRES prior kb_biz_card__session__login call with same account_link_id. Initialize KB Biz Card approvals 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.9/5.0
Behavior4/5

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

Annotations already establish read-only/non-destructive behavior, and the description adds meaningful context: authentication prerequisite, token cost per call ('호출마다 토큰 1소진'), idempotency behavior after a lost response, and that re-calling without the key is a new request. It does not describe return values or follow-on flow, but the behavioral profile is substantially richer than annotations alone.

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 front-loaded and useful, but the idempotency explanation is repetitive ('same arguments only to recover that request' / 'calling again remains a new request'), and the line about 'anonymous taste calls' is confusing and likely a template artifact. The Korean token-cost line is useful but abrupt.

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, the description does a good job covering prerequisites, date-range scope, idempotency, and token cost. It still lacks guidance on what happens after initialization and how it connects to the approvals page/result/search siblings.

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% and most parameters are well documented in the schema. The description adds real semantic depth for request_idempotency_key, explaining recovery use versus new execution and distinguishing it from provider-specific idempotency_key fields.

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: 'Initialize KB Biz Card approvals inquiry for a date range.' This clearly separates it from page/result/search siblings by naming an initialization step, though it does not explicitly contrast with those siblings.

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 a hard prerequisite ('REQUIRES prior kb_biz_card__session__login call with same account_link_id') and explains when to reuse the idempotency key versus use a new one. It does not explicitly say when to call this versus approvals__search or approvals__page, but the init semantics are clear.

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