Skip to main content
Glama

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

hometax__tax__withholding__regular_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__regular_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.9/5.0
Behavior4/5

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

Beyond the annotations it discloses concrete costs and side effects: 1 token per call, an XBOSS task is created and its result stored, the call is not purely read-only, and institution-data changes follow per-tool confirmation procedures. This is consistent with readOnlyHint=false and destructiveHint=false and adds real operational context the annotations do not carry. Only the return shape/pagination behavior is left undisclosed.

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 no-login/no-account point is stated twice in near-identical sentences, and one clause ('호출마다 토큰 1소진 요청 처리 시 XBOSS 작업을 생성하고...') is a garbled concatenation that costs the reader effort. The front-loading is good, but the paragraph carries redundant and awkwardly merged sentences that should be trimmed.

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 1-parameter, zero-required tool with no output schema, the description covers purpose, invocation prerequisites, cost, side effects, and idempotency handling. The only meaningful gap is that it never hints at what the returned 'requirements' content looks like, which matters since there is no output schema.

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?

With 100% schema coverage the baseline is 3, but the description goes further: it explains the retry semantics (same value only to recover an unanswered request, new value for a fresh run, omitting it means a new request), the anonymous-call restriction, and explicitly warns that this field is NOT the institution-side idempotency_key. That meaning is not derivable from the schema alone.

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+resource: it tells the caller what inputs and preparation materials each step of the 원천세 정기신고 requires, and explicitly scopes it to the regular (정기) filing. It does not contrast itself with the amendment_report__requirements or late_report__requirements siblings, so an agent must rely on the tool name alone to distinguish those.

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 ('다른 단계보다 먼저 부르세요' – call this before the other steps), which tells the agent this is a pre-step companion to init/preview/save/submit. It also states the call works without login or account linking, plus the separate rule for anonymous/preview calls. It stops short of naming when NOT to use it or which sibling handles amendment/late filings.

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