Skip to main content
Glama

홈택스 원천세 전자파일 변환신고 준비자료 안내

hometax__tax__withholding__file_conversion__requirements

자격증명이나 로그인 없이 바로 호출할 수 있습니다. 원천세 전자파일 변환신고의 단계마다 필요한 입력과 준비자료, 원본 파일을 등록하는 방법을 알려 줍니다. 기관에 접속하지 않고 계정 연결도 필요 없습니다. 다른 단계보다 먼저 부르세요. 로그인한 호출이면 첫 요청 전에 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": "hometax__tax__withholding__file_conversion__requirements"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A4.1/5.0
Behavior4/5

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

The annotations declare readOnlyHint=false with destructiveHint=false, and the description meaningfully adds beyond them: each call consumes one token, creates an XBOSS job, stores the processing result, and is explicitly stated not to be pure read-only regardless of whether the agency source is queried. That directly supports the non-read-only annotation without contradiction. It stays vague about what actually changes on the agency side ("도구별 실행 내용과 기존 확인 절차를 따릅니다"), which keeps it below a 5.

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 ordering instruction is front-loaded, which is good, but the opening two sentences say the same thing twice about not needing credentials or an account connection. The idempotency block, while useful, is dense and repeats the reuse rule across several sentences, so some pruning would improve it.

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 single-optional-parameter guidance tool with no output schema, the description covers the essentials: what it returns conceptually, that it is safe to call without auth, its ordering relative to sibling steps, the token cost, and the idempotency contract. Only the shape of the returned guidance is unspecified, which is a minor gap given the tool's advisory nature.

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 already 100%, so the baseline is 3, but the description goes well beyond the schema: it explains that the key must be minted and stored before the first request, reused only to recover a request whose response was lost, replaced with a new value for a new execution, that resending without it creates a new request, that the field is unavailable in unauthenticated preview mode, and that the agency's own idempotency_key field is a different field to leave alone. This is substantive semantics an agent could not infer from 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 names a specific verb and resource: it tells the agent the inputs, preparation materials, and original-file registration method required at each step of a withholding-tax electronic file conversion filing. It also distinguishes itself from the sibling step tools by stating it should be called before other steps, though the wording is verbose rather than crisp.

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 gives explicit ordering guidance ("다른 단계보다 먼저 부르세요") that places this call ahead of the other file_conversion steps, and it clarifies that no credentials or login are required. It stops short of naming a specific alternative for cases where requirements are already known, so no explicit when-not-to-use case is stated.

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