Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

지방세 고지 및 미납 내역 조회

wetax__tax__local__due__query

조회만 합니다. 지방세 고지 및 미납 내역을 조회하며 납부나 신고는 수행하지 않습니다. 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

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": {
      "account_link_id": "<account_link_id>",
      "start_month": "<start_month>",
      "end_month": "<end_month>"
    },
    "name": "wetax__tax__local__due__query"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_noNo조회할 페이지 번호입니다. 첫 페이지는 1입니다.
end_monthYes조회 종료 연월입니다. YYYYMM 형식입니다.
tax_codesNo조회할 세목 코드 목록입니다. 비우면 전체 세목입니다.
start_monthYes조회 시작 연월입니다. YYYYMM 형식입니다.
arrears_onlyNo체납 항목만 조회할지 여부입니다.
province_codeNo조회할 시도 코드입니다.
account_link_idYes
municipality_codeNo조회할 시군구 코드입니다.
assessment_type_codesNo기관 과세구분 코드입니다. 기본값은 실제 조회 화면의 전체 선택(1, 2, 3)입니다.
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.
include_automatic_paymentNo자동납부 대상 포함 여부입니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only supply readOnlyHint=false, destructiveHint=false, openWorldHint=false; the description goes well beyond them by disclosing a per-call token cost, that an XBOSS task is created and its result stored, and that the call is not a pure read even though it only retrieves data. It also explains idempotency recovery semantics and that the provider-specific key is a different field. The only weakness is that this operational detail is buried in dense mixed-language prose rather than structured.

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 scope statement is correctly front-loaded, but the body mixes Korean and English awkwardly and packs idempotency rules, token cost, XBOSS behavior, and a generic mutation caveat into one undifferentiated block. The final sentence about 기관 데이터 변경 is boilerplate that does not apply to a retrieval tool and costs the reader time.

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?

With 11 parameters and no output schema, the description carries responsibility for describing what comes back, but it says nothing about the returned notice/arrears records or pagination behavior driven by page_no. The operational side (cost, side effects, idempotency) is well covered, so the omission is a gap rather than a failure.

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 91%, so most parameters are already documented, and the baseline would be 3. The description nonetheless adds real meaning for the one parameter the schema defers to it (request_idempotency_key): when to reuse it, when to mint a new one, that it is unavailable to anonymous calls, and that a provider key must not be conflated with it.

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?

"지방세 고지 및 미납 내역을 조회" names a specific resource (local tax notices/arrears) and a specific operation (query). It also explicitly rules out payment and filing ("납부나 신고는 수행하지 않습니다"), which separates it from the payment and refund siblings. It stops short of naming which sibling query (payment history, refund) to prefer for adjacent data.

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

Usage Guidelines3/5

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

The description sets a clear scope boundary (read-only retrieval, no payment/filing) and gives detailed guidance on when to reuse versus regenerate the idempotency key. However, it never tells the agent when to choose this tool over wetax__tax__local__payment__history__query or wetax__tax__local__refund__query, leaving the sibling routing implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All XBOSS toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources