Skip to main content
Glama

일일 현금영수증 발행 내역 조회

hometax__cash_receipt__daily_issue__search

먼저 호출할 도구: hometax__session__login (같은 account_link_id). 하루치 현금영수증 발급 내역을 조회합니다(당일 발급 조회). trs_dt 는 선택이며, 넣지 않으면 오늘입니다. 이 조회는 당일 자료만 지원하므로 다른 날짜는 조회하지 않습니다. 건수: totalCount(pageInfoVO.totalCount 도 같은 값)는 이 조회의 전체 건수이며 이 응답의 행 수보다 적지 않습니다. collectionMeta 는 이 응답이 이미 전부를 담았는지(complete)와 몇 건이 왔는지(collectedCount)를 알려 줍니다. complete 가 false 면 다음 쪽을 요청합니다. 로그인한 호출이면 첫 요청 전에 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__cash_receipt__daily_issue__search"
  }
}

Input Schema

NameRequiredDescriptionDefault
trs_dtNo거래일자 YYYYMMDD (예: 20250731). 입력하지 않으면 오늘입니다.
page_numNo쪽 번호. 기본 1.
page_sizeNo한 쪽에 받을 건수. 기본 10.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
request_idempotency_keyNo로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / page_num / description
      Previous value: -"Page number (default 1)"New value: +"쪽 번호. 기본 1."
    • changedInput schema / properties / page_size / description
      Previous value: -"Page size (default 10)"New value: +"한 쪽에 받을 건수. 기본 10."
    • changedInput schema / properties / trs_dt / description
      Previous value: -"Transaction date YYYYMMDD (e.g. 20250731). Optional — defaults to today."New value: +"거래일자 YYYYMMDD (예: 20250731). 입력하지 않으면 오늘입니다."
  2. 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: +"로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다."
  3. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, and the description reinforces rather than contradicts them by stating the call is 'not purely read-only' and that it creates an XBOSS task and stores a processing result. It further discloses a per-call cost of 1 token, the guest/trial restriction on request_idempotency_key, the retry-vs-new-request semantics of that key, and the distinct agency-side idempotency_key field. These are non-obvious operational traits an agent could not derive from the annotations or schema.

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 purpose and prerequisite are correctly front-loaded, but the body is long and runs together several unrelated topics (response completeness metadata, idempotency key lifecycle, guest restrictions, token cost, XBOSS task creation, agency confirmation procedures) without structure or headings. Sentences like the reminder about the separate agency idempotency_key field are useful but add bulk that makes the core instruction harder to scan.

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, and the description compensates by explaining the return shape: totalCount/pageInfoVO.totalCount as the total, and collectionMeta.complete/collectedCount indicating whether the response is exhaustive and how to page when complete is false. Combined with the login prerequisite, the same-day-only limit, the token cost, and the idempotency protocol, an agent has everything needed to call and page this tool 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 the baseline is 3, but the description adds real meaning on top: trs_dt's default is restated with the constraint that only today is actually queryable, and the request_idempotency_key field is fully explained here because its schema entry explicitly defers usage to the description. The pagination parameters page_num/page_size get no extra explanation beyond the schema, which keeps it from a 5.

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 gives a specific verb and resource: one day's cash receipt issuance history ('하루치 현금영수증 발급 내역을 조회합니다'), plus the scope constraint that only same-day data is supported. That separates it from cancel/modify/issue siblings and from the purchase/sales history searches. It stops short of naming which sibling to use instead when the caller wants a non-today date or a different receipt category, so it is clear but not fully differentiating.

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?

It states a hard prerequisite ('먼저 호출할 도구: hometax__session__login', same account_link_id), explains that trs_dt is optional and defaults to today, and explicitly says not to query other dates. What it lacks is routing guidance against the many sibling search tools (purchase/sales history, summary), leaving the agent to infer which lookup fits a given request.

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