Skip to main content
Glama

근로복지공단 보험료 부과고지 상세

comwel__info__premium_billing_notice__detail
Read-only

REQUIRES prior comwel__auth__npki_session__login call with same account_link_id. Fetch COMWEL premium billing notice detail. Files: a document generated from this result, as Excel (xlsx) only when requested in output_formats, listed in artifacts[] of the result with a download_url that works for 15 minutes; each file is kept for 7 days. If a link has expired, call xdata__job__result with the job_id from the result for fresh links. For an anonymous result, keep its private recovery_receipt and send it with the original job_id or pack_run_id to xdata__job__result. It grants access to that result only, until the original file retention expires. Do not publish it. Losing it cannot be repaired by signing up. The receipt also works if the client later signs in; it does not grant access to other results. Without a receipt, results require the original account and lane. 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소진

Input Schema

NameRequiredDescriptionDefault
detail_keysYesDetail keys to fetch. Pass the objects from the search result's `detail_candidates` array as-is (filter by insurance_key when needed).
worker_nameNoWorker name filter (optional)
detail_contextYesSearch context. Pass the search result's `detail_context` object as-is.
insurance_typeNoInsurance type filter. Required only when detail_keys mixes both types.
output_formatsNoOptional. Also return this result as a file (Excel (xlsx)) in artifacts[] of the result. Omit it for data only.
account_link_idNoAccount link ID (UUID v4). Optional — the server auto-resolves from your API key when omitted. Provide explicitly only when you have multiple certificates for the same provider. Each institution has a separate ID (Hometax != NHIS != NPS != FourInsure).
worker_resident_noNoWorker resident registration number filter (optional)
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / request_idempotency_key
      Added value: +{
      +  "description": "Optional same-request recovery key for authenticated calls; see the tool description.",
      +  "maxLength": 128,
      +  "minLength": 1,
      +  "pattern": "^[\\x20-\\x7E]+$",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / output_formats
      Added value: +{
      +  "description": "Optional. Also return this result as a file (Excel (xlsx)) in artifacts[] of the result. Omit it for data only.",
      +  "items": {
      +    "enum": [
      +      "xlsx"
      +    ],
      +    "type": "string"
      +  },
      +  "minItems": 1,
      +  "type": "array",
      +  "uniqueItems": true
      +}
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond annotations: discloses file generation behavior (xlsx only when requested, 15-minute download_url, 7-day retention), anonymous result recovery_receipt semantics, idempotency key usage, and per-call token cost. Annotations already mark it read-only, but the description adds rich operational context without contradicting them.

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?

Front-loads the key requirement, but the description is long and somewhat unstructured, mixing file behavior, recovery instructions, and idempotency in a single block. Some sentences could be consolidated without losing meaning.

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?

Covers auth prerequisites, artifact generation, expired-link recovery, anonymous receipt handling, and idempotency semantics thoroughly. However, with no output schema, it does not describe the actual billing notice data returned, leaving a gap for the agent to understand the response payload.

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 adds meaningful usage details for request_idempotency_key (generation, reuse, anonymous unavailability) and output_formats (artifact behavior) that go beyond the schema text.

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?

States a specific verb and resource: 'Fetch COMWEL premium billing notice detail.' The schema references a prior search result, but the description does not explicitly name the sibling search tool or distinguish this detail tool from other detail tools like comwel__info__individual_billed_premium__detail.

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?

Explicitly states the prerequisite login call and gives recovery guidance via xdata__job__result for expired links and anonymous results. However, it never says when to use this tool versus the search tool or other detail alternatives, leaving some inference required.

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