Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

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

hometax__cash_receipt__daily_issue__search
Read-only

REQUIRES prior hometax__session__login call with same account_link_id. Search cash receipt issuance records for a single day (당일 발급 조회). trs_dt is optional; omitting it means today. The adapter documents this endpoint as same-day only, so other dates are not a supported lookup. 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소진

Input Schema

NameRequiredDescriptionDefault
trs_dtNoTransaction date YYYYMMDD (e.g. 20250731). Optional — defaults to today.
page_numNoPage number (default 1)
page_sizeNoPage size (default 10)
account_link_idNoAccount 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).
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations, the description discloses authentication requirements, same-day-only behavior, token cost per call ('호출마다 토큰 1소진'), pagination completeness via collectionMeta, and detailed idempotency-key semantics. These are substantial behavioral details that an agent needs before invoking the tool.

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 description is front-loaded with the critical prerequisite and purpose, and every section is relevant to correct invocation. The idempotency explanation is lengthy but necessary for this tool; overall the structure is efficient, though slightly verbose in the idempotency paragraph.

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?

Given the tool's complexity (auth requirement, pagination, idempotency, same-day restriction) and the absence of an output schema, the description covers all essential context. It explains how to interpret totalCount and collectionMeta and when to request the next page, leaving no major gaps for an agent.

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 parameters are already documented. The description still adds meaningful context: trs_dt defaults to today and only same-day is supported, and request_idempotency_key has extensive usage rules that go beyond the schema's brief pointer. Page parameters receive no extra elaboration, keeping 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 states a specific verb and resource: 'Search cash receipt issuance records for a single day (당일 발급 조회).' It clarifies the scope with 'same-day only' and 'other dates are not a supported lookup,' which helps distinguish it from broader cash receipt history tools. However, it does not explicitly name sibling alternatives like purchase or sales search history, so it falls short of full sibling differentiation.

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 clear prerequisite ('REQUIRES prior hometax__session__login call with same account_link_id') and an explicit usage constraint ('same-day only, so other dates are not a supported lookup'). It does not point to an alternative tool for other date ranges, which keeps it from a 5.

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