Skip to main content
Glama

KB국민카드 부서 선택

kb_biz_card__common__departments__select

먼저 호출할 도구: kb_biz_card__session__login (같은 account_link_id). 지금 세션에서 고를 수 있는 부서 목록을 돌려줍니다. department_name 을 넣으면 그 이름으로 부서를 찾습니다. 로그인한 호출이면 첫 요청 전에 request_idempotency_key 값을 만들어 저장하세요. 응답을 받지 못한 그 요청을 되찾을 때만 같은 인자와 함께 그 값을 다시 보내고, 새로 실행할 때는 새 값을 쓰세요. 이 값 없이 다시 부르면 새 요청이 됩니다. 계정 없이 맛보기로 부를 때는 이 선택 칸을 쓸 수 없습니다. 기관 업무에 따로 있는 idempotency_key 칸은 다른 칸이니 그대로 두세요. 호출마다 토큰 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__departments__select"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
department_nameNo선택 입력. 부서 이름. 넣으면 그 이름의 부서로 좁힙니다.
request_idempotency_keyNo로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / department_name / description
      Previous value: -"Department name filter"New value: +"선택 입력. 부서 이름. 넣으면 그 이름의 부서로 좁힙니다."
  2. Changed1 schema field changed
    • changedInput schema / properties / request_idempotency_key / description
      Previous value: -"Optional same-request recovery key for authenticated calls; see the tool description."New value: +"로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다."
  3. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, and the description importantly explains WHY a 'select' tool is not read-only: each call consumes one token and creates an XBOSS task that stores processing results. That reconciles the surprising non-read-only flag and adds real cost/side-effect disclosure. However, it does not say whether the created task or stored results are visible or how to retrieve them, so the behavioral picture stops short of complete for a write-flagged tool.

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?

It is front-loaded with the prerequisite and the purpose, so an agent can act on the first two sentences. The idempotency paragraph is dense and repeats itself slightly, and the closing sentences about XBOSS task creation and institution-side confirmation procedures read as boilerplate, but nothing is outright filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter, zero-required selection tool with no output schema, this covers purpose, prerequisite, return content, the trial-mode exclusion, idempotency recovery, per-call cost, and side effects. An agent has everything needed to call it correctly on the first attempt.

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, but the description adds meaning the schema does not: account_link_id must match the one used at login, and it carries the full usage rules for request_idempotency_key that the schema explicitly defers to ('쓰는 법은 도구 설명에 있습니다'). department_name is confirmed as an exact-name narrowing filter.

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 concrete verb and resource: it returns the list of departments selectable in the current session, optionally narrowed by department_name. This is unmistakable against the sibling tools, although it never explicitly contrasts itself with the similarly named cards__select.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names the mandatory prerequisite (call kb_biz_card__session__login first with the same account_link_id), explains the idempotency-key workflow in detail, and gives an explicit when-not case: the selection field cannot be used for unauthenticated trial calls. Recovery vs. fresh-execution behavior is spelled out rather than left to inference.

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