XBOSS

국세청 사업자등록 상태 조회

opendata__nts__status

Read-only

Look up NTS business registration status (data.go.kr 15081808). Platform service key only — no account_link_id. 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
`b_no`	Yes	사업자등록번호 목록 - 각 10자리 숫자(예: ["1234567890"]). 최대 100건.
`output_formats`	No	Optional. Also return this result as a file (Excel (xlsx)) in artifacts[] of the result. Omit it for data only.
`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 10, 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
+}

Changed1 schema field changedSep 28, 2026

changedInput schema / properties / b_no / description

Previous value: -"Business registration number(s), 10 digits each (e.g. [\"1234567890\"]). Max 100."New value: +"사업자등록번호 목록 - 각 10자리 숫자(예: [\"1234567890\"]). 최대 100건."

First observedSep 22, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Beyond the readOnlyHint and destructiveHint annotations, the description discloses meaningful behavioral details: artifact download links expire after 15 minutes, files are retained for 7 days, recovery receipts grant access only to that result, and each call consumes one token. These are useful operational traits that an agent would not know from the annotations alone. It does not contradict the read-only annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description front-loads the purpose well, but it then becomes a long run-on block mixing file retention, private recovery receipts, idempotency keys, provider-specific key distinctions, anonymous-call restrictions, and token cost. Much of this is operational boilerplate rather than tool-specific guidance, making the definition unnecessarily bloated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only lookup tool with no output schema, the description covers invocation constraints, artifact behavior, retention, and recovery well enough to call the tool. However, it does not describe what the NTS status result actually contains, leaving the core return semantics underspecified despite extensive artifact and idempotency context.

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 already 100%, so the schema fully documents b_no, output_formats, and request_idempotency_key. The description still adds non-schema semantics for request_idempotency_key, including when to generate it, when to reuse it, and that it is unavailable to anonymous calls, and it reinforces output_formats as the only way to request an xlsx artifact.

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 first sentence clearly states the verb and resource: lookup NTS business registration status, with the data.go.kr dataset ID. It does not distinguish this from the sibling opendata__nts__validate tool, so sibling differentiation is left implicit rather than explicit.

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?

The description gives detailed operational guidance for file artifacts, recovery receipts, and idempotency keys, but it never states when to choose this status lookup versus related tools such as opendata__nts__validate or hometax business registration searches. Usage for the core lookup is implied rather than compared against alternatives.

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?