Skip to main content
Glama

국민연금 결정내역 안내 조회

nps_edi__b1__national_pension_premiums__guide

먼저 호출할 도구: 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__national_pension_premiums__guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
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. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false but say nothing about why; the description supplies the reason, stating that each call consumes one token and that request processing creates an XBOSS job and stores its result, so the call is not purely read-only even though the underlying institution query is a read. It also warns not to confuse request_idempotency_key with the institution's separate idempotency_key field. The closing line about institution data changes following per-tool procedures is generic boilerplate rather than real disclosure.

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 padded: idempotency instructions are restated twice (in the description and again in the schema), and the trailing sentence about institution change procedures is filler. Several sentences could be merged without losing information.

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 two-parameter read-shaped lookup with no output schema, the description covers the things an agent would otherwise get wrong: the required prior login, the idempotency-retry protocol, the token cost, and the hidden job-creation side effect. It does not indicate what the notice response contains, which is the main remaining gap given the absent output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are already fully documented in the schema, establishing a baseline of 3. The description adds one genuinely useful cross-parameter constraint (account_link_id must match the login call) and clarifies that request_idempotency_key is unusable for accountless trial calls, but it adds no syntax, format, or validation detail beyond the schema.

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+resource: look up the national pension premium determination-details notice (결정내역 안내문). It is not a tautology of the title, but it does not differentiate itself from adjacent lookups such as support_details or payment_history, so the agent still has to infer which premium lookup returns which document.

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

Usage Guidelines3/5

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

Strong on prerequisites: it names nps_edi__auth__npki_session__login as the first call with the same account_link_id, and gives explicit when-to-reuse guidance for request_idempotency_key (only to recover an unacknowledged request, always a new value for a new execution). It gives no guidance, however, on when to choose this notice lookup over the sibling premium tools, and only obliquely notes that the optional field is unusable for unauthenticated trial calls.

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