Skip to main content
Glama

증명서 신청 이력 상세 초기화

fourinsure__b1__certificate__history__detail_init

먼저 호출할 도구: fourinsure__session__login (같은 account_link_id). 증명서 신청 이력 상세 화면의 입력 양식을 불러옵니다. 조회만 합니다. 로그인한 호출이면 첫 요청 전에 request_idempotency_key 값을 만들어 저장하세요. 응답을 받지 못한 그 요청을 되찾을 때만 같은 인자와 함께 그 값을 다시 보내고, 새로 실행할 때는 새 값을 쓰세요. 이 값 없이 다시 부르면 새 요청이 됩니다. 계정 없이 맛보기로 부를 때는 이 선택 칸을 쓸 수 없습니다. 기관 업무에 따로 있는 idempotency_key 칸은 다른 칸이니 그대로 두세요. 호출마다 토큰 1소진 요청 처리 시 XBOSS 작업을 생성하고 처리 결과를 저장합니다. 기관 원본의 조회 여부와 별개로 이 호출은 순수 읽기 전용이 아닙니다. 기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cvrc_no": "<cvrc_no>"
    },
    "name": "fourinsure__b1__certificate__history__detail_init"
  }
}

Input Schema

NameRequiredDescriptionDefault
cvrc_noYes증명서 접수번호. 증명서 신청 이력 목록 조회 결과에서 받습니다.
group_cvrc_noNo그룹 접수번호. 이력 행에 값이 있을 때만 입력합니다.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
request_idempotency_keyNo로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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: +"로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다."
  2. Changed2 schema fields changed
    • changedInput schema / properties / cvrc_no / description
      Previous value: -"Certificate application receipt number (증명서 접수번호). Obtain from certificate.history.list."New value: +"증명서 접수번호. 증명서 신청 이력 목록 조회 결과에서 받습니다."
    • changedInput schema / properties / group_cvrc_no / description
      Previous value: -"Group receipt number (그룹 접수번호). Optional; omit unless the history row carries one."New value: +"그룹 접수번호. 이력 행에 값이 있을 때만 입력합니다."
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations only say readOnlyHint=false, destructive=false, openWorld=false; the description adds substantial context beyond them — token cost per call, XBOSS job creation with stored results, and the explicit warning that this is not purely read-only. The earlier phrase "조회만 합니다" slightly muddies this, but the later sentence explicitly corrects it, so there is no net contradiction.

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 correctly front-loaded, but the body is a long run-on mixing token accounting, XBOSS internals, idempotency protocol, and a field-disambiguation warning. The closing line about institution data changes is generic boilerplate, and "조회만 합니다" followed later by "순수 읽기 전용이 아닙니다" reads as an internal contradiction on first pass.

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 say the call returns an input form, and it covers prerequisites, token cost, idempotency behavior, guest-mode limits, and the write side effect — a lot for a 4-parameter tool. What is missing is the actual relationship to the follow-up `history__detail` call and any hint of the form payload's shape.

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; the description still adds real meaning about `request_idempotency_key` — create it before the first call, resend it only to recover an unanswered request, use a new value for a new execution, and it cannot be used in guest mode. It also ties `account_link_id` to the login call, while correctly warning not to confuse the institution's own idempotency field.

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?

"증명서 신청 이력 상세 화면의 입력 양식을 불러옵니다" gives a specific verb (load form) and resource (certificate application history detail screen), which is far better than restating the title. It does not, however, state how this differs from the sibling `certificate__history__detail`, leaving the init/execute split implicit.

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 front-loads an explicit prerequisite ("먼저 호출할 도구: fourinsure__session__login (같은 account_link_id)") and states a guest-mode restriction on the optional idempotency field. It never names a when-not-to-use case or the follow-up detail call, so the routing 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