XBOSS

납부기한 조회/납부

hometax__tax__payment_due__search_or_pay

Read-only

REQUIRES prior hometax__session__login call with same account_link_id. Search tax amounts due by payment deadline (납부할 세액 조회). Read-only: this tool never executes a payment; the 'or_pay' in its name is historical. Files: a document generated from this result, as Excel (xlsx) only when requested in output_formats, listed in artifacts[] of the result with a download_url that works for 15 minutes; each file is kept for 7 days. If a link has expired, call xdata__job__result with the job_id from the result for fresh links. For an anonymous result, keep its private recovery_receipt and send it with the original job_id or pack_run_id to xdata__job__result. It grants access to that result only, until the original file retention expires. Do not publish it. Losing it cannot be repaired by signing up. The receipt also works if the client later signs in; it does not grant access to other results. Without a receipt, results require the original account and lane. 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

Name	Required	Description
`page_num`	No	Page number (default 1)
`page_size`	No	Page size (default 10)
`inqr_cl_cd`	No	Lookup mode (조회구분코드). Optional. '01' shows only items whose payment deadline has passed.
`output_formats`	No	Optional. Also return this result as a file (Excel (xlsx)) in artifacts[] of the result. Omit it for data only.
`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).
`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 14, 2026

addedInput schema / properties / output_formats

Added value: +{
+  "description": "Optional. Also return this result as a file (Excel (xlsx)) in artifacts[] of the result. Omit it for data only.",
+  "items": {
+    "enum": [
+      "xlsx"
+    ],
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array",
+  "uniqueItems": true
+}

First observedSep 22, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the readOnly/destructive annotations: file format constraints (xlsx only when requested), artifact download_url validity of 15 minutes, 7-day file retention, recovery path via xdata__job__result on expiry, and idempotency-key reuse semantics. These are exactly the behaviors that change how an agent retries and recovers.

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 opening two sentences are well front-loaded, but the remainder is a dense block that stacks anonymous-recovery-receipt boilerplate, idempotency rules, provider-key caveats, and token cost into one paragraph. Substantial content is generic pack-wide policy rather than tool-specific guidance, hurting scanability.

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?

Covers auth prerequisite, read-only guarantee, file artifact behavior, and both recovery paths, which is close to complete for a paginated read tool with no output schema. It never characterizes the result records themselves (fields beyond artifacts[]), leaving the agent to infer the payload shape.

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 schema already documents all six parameters and a baseline of 3 applies. The description earns extra credit by supplying the lifecycle semantics for request_idempotency_key (generate before first request, reuse only for lost-response recovery, new key for a new execution) that the schema's one-line pointer does not provide.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (search tax amounts due by payment deadline) and preemptively disambiguates the misleading name: "the 'or_pay' in its name is historical" and read-only. An agent can tell this apart from hometax__tax__payment_statement__search or overdue__search_history without opening a schema.

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?

Explicit prerequisite ("REQUIRES prior hometax__session__login call with same account_link_id") and a clear exclusion (never executes a payment). It does not name an alternative sibling for overlapping query needs, so routing between hometax payment-status tools is left implicit.

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?