Skip to main content
Glama

홈택스 원천세 기한후신고 준비자료 안내

hometax__tax__withholding__late_report__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__late_report__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

A3.7/5.0
Behavior4/5

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

The annotations only declare readOnlyHint=false, openWorldHint=false and destructiveHint=false. This description goes well beyond them by disclosing that each call consumes one token, that processing creates an XBOSS task and stores the result, and that the call is not purely read-only even though no agency original is queried. That last point reconciles with readOnlyHint=false instead of contradicting it. It does not describe the response contents, which is a remaining gap.

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 advice ('call it before other steps') is front-loaded, but the no-login point is stated twice in consecutive sentences. This repetition and the dense idempotency paragraph reduce the clarity of an otherwise organized description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Because this is a requirements-introspection tool with no output schema, the description carries the full burden of explaining returns, and it never says what the reported 'inputs and preparation materials' look like. The call-safety and idempotency behavior is covered well, but the description is only minimally adequate for a tool whose entire value is its output.

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 the single request_idempotency_key parameter is already documented in the schema. The description adds real operational meaning: build and store the value before the first logged-in request, reuse it only to recover an unanswered request, use a new value for a new execution, and do not confuse it with the agency's own idempotency_key field. That is meaningful added context, easily above the baseline for a fully documented 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 specific verb and resource: it reports the inputs and preparation materials required at each step of a withholding-tax late report (원천세 기한후신고). That is concrete enough to distinguish it from the sibling save/submit/preview steps, but it never names a sibling (e.g. late_report__init or late_report__lookup) as the alternative, so differentiation is implied rather than explicit.

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 clear ordering guidance ('call it before other steps') and states that no credentials or account connection are needed, plus the constraint that trial/no-account calls cannot use the optional key field. It stops short of explicitly naming which sibling tool to use instead when this one is not appropriate.

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