Skip to main content
Glama

파일 다운로드

fourinsure__b1__resources__files__download

REQUIRES prior fourinsure__session__login call with same account_link_id. Checks whether the attachment exists and returns its original file name by default (dry-run); no file is included. Send dry_run=false to receive the actual file in the result artifacts. Files: the document the institution issued, unchanged, as Hancom Office (hwp) or PDF, 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소진 요청 처리 시 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": {
      "atfl_id": "<atfl_id>",
      "atch_file_sn": "<atch_file_sn>"
    },
    "name": "fourinsure__b1__resources__files__download"
  }
}

Input Schema

NameRequiredDescriptionDefault
atfl_idYesAttachment file ID
dry_runNoDefault true (dry-run): returns existence and file name only. Set false to receive the actual file in the result artifacts.
atch_file_snYesAttachment file sequence number
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, and the description agrees, explicitly warning that the call is not purely read-only and that an XBOSS job is created and 1 token is consumed per call — useful context beyond the annotations. It also discloses artifact retention (7 days), download_url lifetime (15 minutes), and access scoping for anonymous receipts. It loses a point for burying these facts in a long multi-topic block and for closing Korean boilerplate about institutional data changes that adds no actionable detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is a long run-on that interleaves unrelated concerns: login prerequisite, dry-run/file retrieval, retention windows, expired-link routing, anonymous recovery receipts, idempotency keys, token cost, and internal job creation, with the Korean boilerplate tail. It is not front-loaded, and an agent must parse several paragraphs to find the one decision that matters (dry_run true/false).

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 must carry the return contract, and it does: results arrive in artifacts[] with the original unmodified HWP or PDF, a download_url valid 15 minutes, and 7-day file retention. The prerequisite login and same account_link_id are stated, and expired-link recovery is covered. The anonymous recovery_receipt discussion is disproportionate for a file download and slightly muddies an otherwise complete picture.

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

Parameters5/5

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

Schema coverage is 100%, so atfl_id, atch_file_sn, dry_run, and account_link_id are already documented. The description nonetheless adds real meaning for request_idempotency_key, whose schema entry only says 'see the tool description': it specifies generating and saving the key before the first request, reusing it only to recover a lost response, and using a new key for a new execution — plus the caveat that provider-specific idempotency_key fields are distinct.

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 operation: it checks whether the attachment exists and returns the original file name by default, and with dry_run=false delivers the actual file (hwp/PDF) in artifacts[]. The purpose is clear but not front-loaded — the first sentence is a login prerequisite rather than what the tool does, and the tool's core action is only inferable from the title and the dry_run explanation.

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?

Explicit context is given for the main branching decision (default dry-run vs dry_run=false) and for edge cases: expired links are routed to xdata__job__result with the job_id, and anonymous results are recovered via the private recovery_receipt. It also states the login prerequisite and idempotency-key reuse rules. It does not, however, distinguish this tool from sibling download tools such as fourinsure__b1__certificate__history__pdf_download or hometax__certificate__download.

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