Skip to main content
Glama

지방세 납부내역 조회

wetax__tax__local__payment__history__query

먼저 호출할 도구: wetax__session__login (같은 account_link_id). 조회만 합니다. 지방세 납부 이력과 기관 식별자를 조회하며 납부는 수행하지 않습니다. 로그인한 호출이면 첫 요청 전에 request_idempotency_key 값을 만들어 저장하세요. 응답을 받지 못한 그 요청을 되찾을 때만 같은 인자와 함께 그 값을 다시 보내고, 새로 실행할 때는 새 값을 쓰세요. 이 값 없이 다시 부르면 새 요청이 됩니다. 계정 없이 맛보기로 부를 때는 이 선택 칸을 쓸 수 없습니다. 기관 업무에 따로 있는 idempotency_key 칸은 다른 칸이니 그대로 두세요. 호출마다 토큰 1소진 요청 처리 시 XBOSS 작업을 생성하고 처리 결과를 저장합니다. 기관 원본의 조회 여부와 별개로 이 호출은 순수 읽기 전용이 아닙니다. 기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "wetax__tax__local__payment__history__query"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_noNo조회할 페이지 번호입니다. 첫 페이지는 1입니다.
end_dateYes조회 종료일입니다.
tax_codesNo조회할 세목 코드 목록입니다. 비우면 전체 세목입니다.
start_dateYes조회 시작일입니다.
province_codeNo조회할 시도 코드입니다.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
municipality_codeNo조회할 시군구 코드입니다.
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
Behavior5/5

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

Adds substantial context the annotations cannot convey: per-call token consumption ('호출마다 토큰 1소진'), creation of an XBOSS work item with stored results, and an explicit warning that despite reading institution data the call is not purely read-only — consistent with readOnlyHint=false. The idempotency contract (create before first call, resend same value only to recover an unanswered request, new value for a new execution, otherwise it becomes a new request) is unusually detailed and correctly distinguishes request_idempotency_key from the institution-side idempotency_key field.

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 prerequisite is correctly front-loaded, but several sentences are run-ons or garbled, notably '호출마다 토큰 1소진 요청 처리 시 XBOSS 작업을 생성하고 처리 결과를 저장합니다.' which merges two ideas without punctuation. The idempotency guidance is valuable but occupies five sentences that could be tightened.

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 an 8-parameter read-type query with no output schema, the description covers prerequisites, cost, side effects, retry semantics, and the read/payment distinction; the only real omission is that it never hints at what the response contains (payment records plus institution identifier are only implied by the purpose sentence).

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 already 100%, so the baseline is 3; the description goes beyond it by explaining the operational semantics of request_idempotency_key (recovery-only, cannot be used for anonymous trials) and by warning not to confuse it with the institution's own idempotency_key parameter. It says little extra about date range, tax_codes, or region codes, which the schema already covers.

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?

States a specific verb and resource: '지방세 납부 이력과 기관 식별자를 조회' and explicitly negates payment ('납부는 수행하지 않습니다'), which separates it from payment-execution siblings. It does not name the neighboring query tools (due/refund query) to sharpen the boundary, so it stops short of a 5.

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 a clear prerequisite ('먼저 호출할 도구: wetax__session__login (같은 account_link_id)') and a constraint for anonymous use ('계정 없이 맛보기로 부를 때는 이 선택 칸을 쓸 수 없습니다'). It does not state when to prefer this over the sibling due/refund history queries, so exclusions from alternatives are missing.

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