Skip to main content
Glama

전자세금계산서 합계 조회

hometax__etax__invoice__search_summary

먼저 호출할 도구: hometax__session__login (같은 account_link_id). 전자세금계산서 합계를 조회합니다. 날짜 방식은 하나만 고릅니다. (1) 일별: date_type='01' 과 start_date, end_date(YYYYMMDD). (2) 월별: date_type='02' 와 year, month. (3) 분기별: date_type='03' 과 year, quarter. search_type 은 '01' 이 발급한 것(매출), '02' 가 받은 것(매입)입니다. 로그인한 호출이면 첫 요청 전에 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": "hometax__etax__invoice__search_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoYear (e.g. 2025). Required when date_type='02' (monthly) or '03' (quarterly).
monthNoMonth 1-12. Required when date_type='02' (monthly).
quarterNoQuarter 1-4. Required when date_type='03' (quarterly).
end_dateNoEnd date YYYYMMDD (e.g. 20250930). Required when date_type='01' (daily).
date_typeNoDate mode: '01'=daily(default, needs start_date/end_date), '02'=monthly(needs year+month), '03'=quarterly(needs year+quarter).
page_sizeNoPage size (default 10)
start_dateNoStart date YYYYMMDD (e.g. 20250701). Required when date_type='01' (daily).
search_typeNo'01'=issued(매출, default), '02'=received(매입).
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.3/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false; the description explains why a search consumes 1 token per call, creates an XBOSS job and stores its result, and explicitly warns the call is not purely read-only regardless of the source system's read behavior. It also discloses the retry contract: reuse the same request_idempotency_key with identical arguments only to recover an unanswered request, otherwise a new key produces a new request.

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 is front-loaded and the three date modes are cleanly enumerated, which suits a complex tool. The closing sentence about institutional data changes follows the tool's own execution steps is generic boilerplate that adds little for this specific tool.

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 no output schema and 10 parameters, the description never says what the summary returns (totals, counts, grouping, approval status) nor how page_size behaves in a summary tool, which is a notable gap. Input-side behavior, prerequisites, and retry semantics are otherwise covered thoroughly.

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 the baseline is 3, but the description adds real meaning: it documents how request_idempotency_key is meant to be used (the schema itself defers to the tool description for this) and clarifies that the institution-side idempotency_key field is a different field to leave untouched. The mention of a field that is not in this schema adds slight noise but is clarifying context.

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 opens with a specific verb and resource ("전자세금계산서 합계를 조회합니다") and the word 합계 distinguishes it from the list/detail siblings in spirit. It does not explicitly name which sibling to prefer over search_statistics or search_list, so a 4 rather than 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 Guidelines5/5

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

It states the prerequisite call (hometax__session__login with the same account_link_id), enforces exclusive selection of exactly one date mode with the exact parameter triple for each, and defines search_type as sales ('01') vs purchase ('02'). It also says the idempotency key cannot be used for anonymous/trial calls, which is an explicit when-not rule.

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