Skip to main content
Glama

지방소득세 특별징수 신고 시작

wetax__tax__local_income__special_withholding__init

먼저 호출할 도구: wetax__session__login (같은 account_link_id). 조회만 합니다. 로그인한 사업장이 특별징수 신고를 할 수 있는지, 신고할 사업장(사업자등록번호 일부 가림, 상호, 관할 지자체 코드), 저장 단계마다 넣을 값과 막힌 사유를 돌려줍니다. 신고서는 만들지 않습니다 - 신고서는 신고인 저장이 처음 만듭니다. 로그인한 호출이면 첫 요청 전에 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": "wetax__tax__local_income__special_withholding__init"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
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.8/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false, destructiveHint=false, openWorldHint=false. The description goes well beyond that: it discloses a token cost per call, that an XBOSS work item is created and results are stored, and explicitly reconciles the apparent read-only nature of the query with the fact that the call is not purely read-only. It also explains the idempotency retry semantics and that a separate institutional idempotency_key field must be left alone.

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

Conciseness4/5

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

The prerequisite and the read-only scope are front-loaded, and most sentences carry distinct information. There is some redundancy, e.g. '이 값 없이 다시 부르면 새 요청이 됩니다' restates the preceding reuse rule, and the idempotency discussion is dense, but nothing is seriously misplaced.

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

Completeness5/5

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

There is no output schema, so the description must describe the return values, and it does: eligibility, masked business number, trade name, local government code, per-step save values, and blocking reasons. Combined with the prerequisite, cost, and idempotency disclosures, an agent has everything needed to call it correctly.

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?

Schema coverage is 100%, so both parameters are already documented. The description still adds real meaning beyond the schema: it explains that account_link_id must match the login call, and gives the operational rule for request_idempotency_key (reuse only to recover an unanswered request, new value for a fresh run, and that omitting it creates a new request).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action and resource: it checks whether the logged-in business can file a special withholding report and returns the business registration number (partially masked), trade name, local government code, per-step save values, and blocking reasons. It also explicitly distinguishes itself from the sibling that actually creates the report ('신고서는 만들지 않습니다 - 신고서는 신고인 저장이 처음 만듭니다'), so an agent can tell it apart from declarant_save without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names the prerequisite tool and the matching argument ('먼저 호출할 도구: wetax__session__login (같은 account_link_id)'), states the exclusion (this tool does not create the report), and gives explicit rules for when to reuse the idempotency key versus generate a new one. It also notes the key is unavailable for unauthenticated trial calls.

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