Skip to main content
Glama

연금보험료 고지 목록 조회

nps_edi__b1__pension_notices__search

먼저 호출할 도구: nps_edi__auth__npki_session__login (같은 account_link_id). 연금보험료 고지 목록을 조회합니다. 로그인한 호출이면 첫 요청 전에 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": "nps_edi__b1__pension_notices__search"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_noNo쪽 번호. 기본 1.
end_dateNo조회 종료일 YYYYMMDD.
start_dateNo조회 시작일 YYYYMMDD.
template_codeNo서식 코드.
page_per_countNo한 쪽에 받을 건수. 기본 10.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
installment_roundNo회차.
notice_year_monthNo고지 연월 YYYYMM.
row_text_containsNo행의 글자에 이 값이 들어 있는 행을 고릅니다.
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. Changed8 schema fields changed
    • changedInput schema / properties / end_date / description
      Previous value: -"End date YYYYMMDD"New value: +"조회 종료일 YYYYMMDD."
    • changedInput schema / properties / installment_round / description
      Previous value: -"Installment round (회차)"New value: +"회차."
    • changedInput schema / properties / notice_year_month / description
      Previous value: -"Notice year-month YYYYMM"New value: +"고지 연월 YYYYMM."
    • changedInput schema / properties / page_no / description
      Previous value: -"Page number (default: 1)"New value: +"쪽 번호. 기본 1."
    • changedInput schema / properties / page_per_count / description
      Previous value: -"Items per page (default: 10)"New value: +"한 쪽에 받을 건수. 기본 10."
    • changedInput schema / properties / row_text_contains / description
      Previous value: -"Partial row text match"New value: +"행의 글자에 이 값이 들어 있는 행을 고릅니다."
    • changedInput schema / properties / start_date / description
      Previous value: -"Start date YYYYMMDD"New value: +"조회 시작일 YYYYMMDD."
    • changedInput schema / properties / template_code / description
      Previous value: -"Template code (서식 코드)"New value: +"서식 코드."
  3. 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 concrete cost and side effects: one token consumed per call, an XBOSS task created and its result stored on each request. Crucially it explains why readOnlyHint=false — the call is not purely read-only even though the underlying institution lookup is — so the annotation is justified rather than merely asserted. It also spells out retry semantics for recovering an unanswered request.

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 and purpose are correctly front-loaded, but the idempotency block runs four sentences with some restatement ("이 값 없이 다시 부르면 새 요청이 됩니다" repeats the preceding rule). The closing sentence about institution data changes following per-tool procedures is vague filler that adds little.

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 ten all-optional, fully described parameters and no output schema, the description supplies the pieces the schema cannot: auth prerequisite, per-call cost, side-effect creation, and idempotency protocol. Filter semantics (dates, notice year-month, installment round) are left entirely to the schema, which is acceptable at 100% coverage.

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 earns above that by fully explaining request_idempotency_key — which the schema itself defers to the description — including generate-before-first-call, reuse-only-to-recover, and new-value-per-execution. It also warns that this field is distinct from the institution's own idempotency_key field, preventing a likely misuse.

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?

"연금보험료 고지 목록을 조회합니다" names a specific verb (조회) and resource (연금보험료 고지 목록), and the preceding sentence pins the prerequisite login tool. It does not differentiate against close siblings such as pension_notices__select or pension_notification_documents__search, so an agent must still infer which listing tool fits.

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 states explicitly what to call first (nps_edi__auth__npki_session__login with the same account_link_id) and when the optional idempotency field may and may not be used (not for anonymous trial calls). It gives no guidance on when to pick this search over the sibling select/detail tools.

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