XBOSS

현금영수증 매출 내역 조회

hometax__cash_receipt__sales__search_history

REQUIRES prior hometax__session__login call with same account_link_id. Search cash receipt sales history. from_date/to_date are required (YYYYMMDD or YYYY-MM-DD). Counts: totalCount (and the same value in pageInfoVO.totalCount) is the record count for this query and is never fewer than the rows in this response; collectionMeta says whether this response already holds all of them (complete) and how many came back (collectedCount). When complete is false, ask for the next page. 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 작업을 생성하고 처리 결과를 저장합니다. 기관 원본의 조회 여부와 별개로 이 호출은 순수 읽기 전용이 아닙니다. 기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다.

Input Schema

Name	Required	Description
`to_date`	Yes	End date YYYYMMDD or YYYY-MM-DD (e.g. 20260131). Required.
`page_num`	No	Page number (default 1)
`from_date`	Yes	Start date YYYYMMDD or YYYY-MM-DD (e.g. 20260101). Required.
`max_pages`	No	Safety cap when fetch_all_pages is true (default 100)
`page_size`	No	Page size (default 10)
`pbl_cl_cd`	No	발행구분(issuance type): 'all'=전체, '1'=사업자, '2'=국세청, '3'=명세서. Default 'all'.
`account_link_id`	No	Account link ID (UUID v4). Optional — the server auto-resolves from your API key when omitted. Provide explicitly only when you have multiple certificates for the same provider. Each institution has a separate ID (Hometax != NHIS != NPS != FourInsure).
`fetch_all_pages`	No	true collects every page instead of one (default false). Each page is a separate NTS request, so it is slower.
`request_idempotency_key`	No	Optional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

addedInput schema / properties / request_idempotency_key

Added value: +{
+  "description": "Optional same-request recovery key for authenticated calls; see the tool description.",
+  "maxLength": 128,
+  "minLength": 1,
+  "pattern": "^[\\x20-\\x7E]+$",
+  "type": "string"
+}

Changed1 schema field changedOct 15, 2026

addedInput schema / properties / pbl_cl_cd

Added value: +{
+  "description": "발행구분(issuance type): 'all'=전체, '1'=사업자, '2'=국세청, '3'=명세서. Default 'all'.",
+  "enum": [
+    "all",
+    "1",
+    "2",
+    "3"
+  ],
+  "type": "string"
+}

First observedSep 22, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Beyond the annotations, it discloses cost ('토큰 1소진' per call), a side effect (creates an XBOSS task and stores results), and explicitly reconciles that with the non-read-only nature of the call, which matches readOnlyHint=false. It also explains the count semantics (totalCount, pageInfoVO.totalCount, collectionMeta.complete/collectedCount) and the idempotency-key recovery model, which is exactly the behavioral context an agent needs before retrying.

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 and the pagination/idempotency guidance is dense but useful. However, the trailing Korean block partially restates the read-only point already made in English, and the sentence about the key not being available to 'anonymous taste calls' appears to be boilerplate carried over from another tool and is noise here.

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?

With no output schema and nine parameters, the description carries a lot of weight and mostly delivers: it explains the response envelope semantics, the multi-page collection model, prerequisites, and retry safety. It does not cover the interaction between fetch_all_pages and max_pages or the enum meaning of pbl_cl_cd, but the schema documents both adequately.

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 baseline is 3, but the description genuinely adds meaning the schema lacks: the relationship between totalCount and returned rows, what complete/collectedCount imply, and the rules for generating, reusing, and not reusing request_idempotency_key (including that it is distinct from a provider-side key). pbl_cl_cd and the paging parameters are left entirely to the schema.

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 states a specific verb and resource ('Search cash receipt sales history'), which is unambiguous on its own. However, it never distinguishes itself from close siblings such as hometax__cash_receipt__purchase__search_history (purchase vs. sales) or hometax__cash_receipt__sales__search_summary (history vs. summary), so an agent must infer the boundary.

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 gives a real precondition ('REQUIRES prior hometax__session__login call with same account_link_id') and concrete follow-up guidance ('When complete is false, ask for the next page'), which is more than most tools offer. It stops short of naming when to prefer a sibling tool or when this search is the wrong choice, so it is clear context without exclusions.

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

All XBOSS tools Inspect

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

Need Help?