Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

전자세금계산서 통계 조회

hometax__etax__invoice__search_statistics
Read-only

REQUIRES prior hometax__session__login call with same account_link_id. Search e-tax invoice monthly statistics. Use wrt_ym_strt/wrt_ym_end in YYYYMM format (e.g. 202507/202509 for July-September 2025). 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
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_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. Changed7 schema fields changed
    • changedInput schema / properties / dt_cl / description
      Previous value: -"'01'=issued(작성일), '02'=received(전송일). Default '01'."New value: +"Aggregation period: '01'=monthly(월별), '02'=quarterly(분기별), '03'=yearly(년도별). Default '01'."
    • changedInput schema / properties / dt_cl / enum
      Previous value: -[
-  "01",
-  "02"
-]New value: +[
+  "01",
+  "02",
+  "03"
+]
    • addedInput schema / properties / etxiv_clsf_cd
      Added value: +{
+  "description": "Invoice classification (전자세금계산서 구분): '01'=tax invoice(전자세금계산서), '03'=invoice(전자계산서). Default '01'.",
+  "enum": [
+    "01",
+    "03"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / ht_rtn_cd_end
      Added value: +{
+  "description": "Quarter end code (분기 종료 코드, e.g. '20254'). Used only when dt_cl=02(quarterly).",
+  "type": "string"
+}
    • addedInput schema / properties / ht_rtn_cd_strt
      Added value: +{
+  "description": "Quarter start code (분기 시작 코드, e.g. '20251'). Used only when dt_cl=02(quarterly).",
+  "type": "string"
+}
    • changedInput schema / properties / wrt_ym_end / description
      Previous value: -"End month YYYYMM (e.g. 202509 for September 2025). NOT a full date."New value: +"End period, same format as wrt_ym_strt (monthly YYYYMM / quarterly YYYY+quarter / yearly YYYY)."
    • changedInput schema / properties / wrt_ym_strt / description
      Previous value: -"Start month YYYYMM (e.g. 202507 for July 2025). NOT a full date."New value: +"Start period. Monthly(dt_cl=01): YYYYMM (e.g. 202507). Quarterly(02): YYYY+quarter code (e.g. 20251). Yearly(03): YYYY."
  3. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), and the description adds genuine non-obvious behavior: session prerequisite tied to account_link_id, idempotency-key recovery semantics for lost responses, and a per-call token cost. The idempotency prose is boilerplate-heavy, but the auth and cost disclosures are exactly what annotations cannot convey.

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?

Front-loads the session prerequisite, which is the right priority. But roughly half the text is generic idempotency-key boilerplate that repeats the schema's own pointer, plus a Korean token-cost line appended at the end rather than integrated into the behavior description.

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 10 parameters, full schema coverage, and read-only annotations, the description covers the pieces an agent most needs: auth prerequisite, key idempotency, and cost. It stops short of describing what the statistics actually contain (there is no output schema), and it omits sibling differentiation, so it is not fully complete.

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

Parameters2/5

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

Schema coverage is 100%, so the baseline would be 3, but the description actively misleads: it says to use wrt_ym_strt/wrt_ym_end "in YYYYMM format" while the schema specifies YYYY+quarter for dt_cl=02 and YYYY for dt_cl=03. An agent following the description would send wrong values for quarterly or yearly aggregation.

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?

States a specific verb+resource ("Search e-tax invoice monthly statistics") that an agent can act on. However, it never distinguishes this tool from close siblings such as hometax__etax__invoice__search_summary, search_list, and search_detail, and calling it "monthly statistics" is narrower than the schema's monthly/quarterly/yearly aggregation.

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?

Gives a real precondition ("REQUIRES prior hometax__session__login call with same account_link_id") and format guidance, which is useful context. But there is no statement of when to prefer this aggregation tool over search_summary or search_list, so the agent must infer the boundary from the name alone.

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