Skip to main content
Glama

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

hometax__tax__withholding__amendment_report__requirements

No credential or login required. 원천세 수정신고의 단계마다 필요한 입력과 준비자료를 알려 줍니다. 기관에 접속하지 않고 계정 연결도 필요 없습니다. 다른 단계보다 먼저 부르세요. 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

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__amendment_report__requirements"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A3.8/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false, destructiveHint=false and openWorldHint=false. The description supplements this usefully: no login or institution connection is needed, each call consumes one token, the call creates and stores an XBOSS task, and it explicitly warns the call is not purely read-only even though it queries rather than writes — consistent with readOnlyHint=false. The idempotency paragraph, while generic boilerplate, also explains replay semantics. Some noise ('anonymous taste calls', provider-specific key wording) dilutes the signal.

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 useful content (no login needed, what is returned, call order) is front-loaded, but a large middle block is generic template text about idempotency keys and XBOSS tasks that does not apply to this single-parameter read-style tool. Phrases like 'not available to anonymous taste calls' and advice about a 'provider-specific idempotency_key' field that does not exist in the schema add confusion rather than value.

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 one-optional-parameter tool with no output schema, the definition conveys what the agent gets back (per-step required inputs and preparation materials) and when to call it. Token cost and task-creation side effects are disclosed. Nothing essential for a correct invocation is missing, though the return shape could be characterized a bit more concretely.

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?

Only one optional parameter exists and the schema already describes it at 100% coverage, so the baseline would be 3. The description adds real meaning: the key is for recovering the same request after a lost response, must be reused only with identical arguments, and a new execution needs a new key.

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 resource and function: it tells the agent that per-step inputs and preparation materials for a withholding amendment report (원천세 수정신고) are returned. The tax-form qualifier separates it from the late_report and regular_report requirements siblings, but no sibling is named explicitly, so the differentiation is implicit rather than spelled out.

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?

"다른 단계보다 먼저 부르세요" gives clear ordering guidance: call this before the other amendment_report steps. However, it never states when NOT to use it or names an alternative (e.g., the late_report or regular_report requirements tools), so exclusions are left to inference.

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