Skip to main content
Glama

KB국민카드 카드 선택

kb_biz_card__common__cards__select

REQUIRES prior kb_biz_card__session__login call with same account_link_id. 지금 세션에서 고를 수 있는 카드 목록을 돌려줍니다. 부서(department_sequence_no, department_name)를 넣어 그 부서의 카드를 조회할 수 있습니다. 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소진 요청 처리 시 XBOSS 작업을 생성하고 처리 결과를 저장합니다. 기관 원본의 조회 여부와 별개로 이 호출은 순수 읽기 전용이 아닙니다. 기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "kb_biz_card__common__cards__select"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
department_nameNoDepartment name filter
department_sequence_noNoDepartment sequence number from departments.select
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, it discloses that each call consumes one token, creates an XBOSS task and stores processing results, and is explicitly not a pure read-only call, which is consistent with readOnlyHint=false. It also spells out idempotency-key lifecycle rules (generate before the first request, reuse only for lost-response recovery, new key for a new execution, and unavailable for anonymous calls).

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 definition is long, bilingual, and mixes task-specific guidance with generic boilerplate about XBOSS task creation and provider data-change procedures that reads as shared template text. The prerequisite is correctly placed first, but the core purpose sentence arrives after the precondition and the boilerplate dilutes it.

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 a four-parameter, non-destructive listing tool with no output schema, the definition covers the prerequisite, the filter semantics, token cost, and side effects. It does not describe the shape of the returned card list or whether results are paginated, which would help an agent decide how to consume the output.

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 description coverage is 100%, so the baseline is 3. The description adds real value beyond the schema for request_idempotency_key, whose schema entry only defers to the tool description, by defining when to create and reuse the key. It also ties account_link_id to the session precondition.

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 second sentence states a specific verb and resource: it returns the list of cards selectable in the current session, optionally scoped to a department. This is distinguishable from the sibling departments.select tool, which is referenced as the source of department_sequence_no. However, the purpose is buried behind a prerequisite sentence rather than front-loaded.

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?

It gives an explicit precondition (a prior kb_biz_card__session__login call with the same account_link_id) and explains how to use the department filter to narrow results. It does not name an alternative tool or state when to skip the department filter entirely, so guidance is clear but not exhaustive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources