Skip to main content
Glama

전자세금계산서 통계 조회

hometax__etax__invoice__search_statistics

REQUIRES prior hometax__session__login call with same account_link_id. 전자세금계산서 통계를 월, 분기, 연 단위로 조회합니다. wrt_ym_strt/wrt_ym_end 는 YYYYMM 형식입니다(예: 2025년 7월부터 9월까지는 202507/202509). 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": {
      "wrt_ym_strt": "<wrt_ym_strt>",
      "wrt_ym_end": "<wrt_ym_end>"
    },
    "name": "hometax__etax__invoice__search_statistics"
  }
}

Input Schema

NameRequiredDescriptionDefault
dt_clNoAggregation period: '01'=monthly(월별), '02'=quarterly(분기별), '03'=yearly(년도별). Default '01'.
page_numNoPage number (default 1)
page_sizeNoPage size (default 10)
wrt_ym_endYesEnd period, same format as wrt_ym_strt (monthly YYYYMM / quarterly YYYY+quarter / yearly YYYY).
wrt_ym_strtYesStart period. Monthly(dt_cl=01): YYYYMM (e.g. 202507). Quarterly(02): YYYY+quarter code (e.g. 20251). Yearly(03): YYYY.
etxiv_clsf_cdNoInvoice classification (전자세금계산서 구분): '01'=tax invoice(전자세금계산서), '03'=invoice(전자계산서). Default '01'.
ht_rtn_cd_endNoQuarter end code (분기 종료 코드, e.g. '20254'). Used only when dt_cl=02(quarterly).
ht_rtn_cd_strtNoQuarter start code (분기 시작 코드, e.g. '20251'). Used only when dt_cl=02(quarterly).
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
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

B3.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false, openWorldHint=false; the description adds real context that they don't: each call burns one token, a XBOSS task is created and the result is stored, and the call '순수 읽기 전용이 아닙니다' — consistent with readOnlyHint=false rather than contradicting it. The idempotency paragraph explains reuse-vs-new-key recovery semantics precisely. It loses a point for the vague closer '기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다', which doesn't say what side effect, if any, occurs on provider data.

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 definition is dominated by a five-sentence generic idempotency boilerplate block and Korean platform boilerplate that applies to every tool in this server, not this one. Purpose and prerequisite are split across English and Korean sentences, so the front-loaded part is a prerequisite rather than the operation, and the reader must wade through tangential notes (anonymous 'taste calls', provider-specific idempotency_key) to reach the substantive facts.

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?

For a 10-parameter tool with no output schema, it covers the auth prerequisite, token cost, idempotency, and period formats. It never describes what the statistics payload contains (aggregated counts, amounts, per-period rows) or how page_num/page_size interact with aggregated results, which an agent needs to pick this over search_summary.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already defines dt_cl, etxiv_clsf_cd, the quarter codes, and the account_link_id fallback, making 3 the baseline. The description's added example (202507/202509 for July–September) is helpful, but the blanket claim 'wrt_ym_strt/wrt_ym_end 는 YYYYMM 형식입니다' is misleading for dt_cl=02 (YYYY+quarter) and dt_cl=03 (YYYY), conflicting with the schema's own required-parameter docs.

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 Korean sentence '전자세금계산서 통계를 월, 분기, 연 단위로 조회합니다' gives a specific verb (조회) and resource (전자세금계산서 통계) plus the aggregation granularity, which separates it from search_list/search_detail. It never names search_summary, the closest sibling, so the agent must infer the boundary between '통계' and '요약'.

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?

It states a hard prerequisite ('REQUIRES prior hometax__session__login call with same account_link_id') and a cost signal ('호출마다 토큰 1소진'). What is missing is any guidance on when to choose this over search_summary/search_list, or any exclusion — usage is only implied by the presence of a prerequisite.

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