Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

국세청 사업자등록 진위 확인

opendata__nts__validate
Read-only

Validate NTS business registration identity (data.go.kr 15081808). Requires b_no, start_dt (YYYYMMDD), p_nm per businesses[] item. Platform service key only — no account_link_id. 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
businessesYes진위 확인 대상 사업자 목록. 항목마다 b_no, start_dt(YYYYMMDD), p_nm 이 필수.
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. Changed1 schema field changed
    • changedInput schema / properties / businesses / items / properties / p_nm2 / description
      Previous value: -"대표자 성명 2(선택)."New value: +"대표자 한글명(선택). 대표자성명(p_nm)이 외국인 영문명일 때만 그 한글명을 넣습니다. 공동대표자명이 아니며, 내국인은 비웁니다."
  3. Changed9 schema fields changed
    • changedInput schema / properties / businesses / description
      Previous value: -"NTS validate businesses[]. Each item requires b_no, start_dt (YYYYMMDD), p_nm."New value: +"진위 확인 대상 사업자 목록. 항목마다 b_no, start_dt(YYYYMMDD), p_nm 이 필수."
    • changedInput schema / properties / businesses / items / properties / b_nm / description
      Previous value: -"Optional business name."New value: +"상호(선택)."
    • changedInput schema / properties / businesses / items / properties / b_no / description
      Previous value: -"Business registration number (10 digits)."New value: +"사업자등록번호(10자리 숫자)."
    • changedInput schema / properties / businesses / items / properties / b_sector / description
      Previous value: -"Optional sector."New value: +"업태(선택)."
    • changedInput schema / properties / businesses / items / properties / b_type / description
      Previous value: -"Optional type."New value: +"종목(선택)."
    • changedInput schema / properties / businesses / items / properties / corp_no / description
      Previous value: -"Optional corporate registration number."New value: +"법인등록번호(선택)."
    • changedInput schema / properties / businesses / items / properties / p_nm / description
      Previous value: -"Representative name (required)."New value: +"대표자 성명(필수)."
    • changedInput schema / properties / businesses / items / properties / p_nm2 / description
      Previous value: -"Optional second name."New value: +"대표자 성명 2(선택)."
    • changedInput schema / properties / businesses / items / properties / start_dt / description
      Previous value: -"Business start date YYYYMMDD."New value: +"개업일자 YYYYMMDD."
  4. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. Beyond that, the description adds meaningful behavior: platform-key-only auth, no account_link_id, a token cost per call, and detailed idempotency-key recovery semantics. These are substantial operational facts not present in the annotations.

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 description is front-loaded with purpose and requirements, which helps. But the idempotency passage is verbose and somewhat repetitive ('Without it, calling again remains a new request'), and the trailing Korean token-cost note feels appended rather than integrated.

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?

It covers auth mode, required fields, idempotency, and token cost, which is strong operational context. But there is no output schema, and the description never explains what a validation response contains (e.g., valid/invalid status or per-business results), which is a meaningful gap for a validation tool.

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 description coverage is 100%, so the baseline is 3. The description nevertheless adds value by explaining the optional request_idempotency_key lifecycle in detail—when to generate it, when to reuse it, and how it differs from provider-specific idempotency keys—which the schema only references tersely.

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 clearly states the specific verb and resource: validate NTS business registration identity, and gives the data.go.kr API ID. It is distinguishable from generic lookups, but it does not explicitly contrast with the sibling opendata__nts__status tool, so it stops short of a 5.

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?

It lists required fields and operational constraints (platform service key only, idempotency key lifecycle), which implies when the tool is appropriate. However, it never states when to use this versus alternatives such as opendata__nts__status or hometax business-registration lookups, leaving routing to inference.

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