Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

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

opendata__nts__status

공공데이터포털에 개방된 국세청 사업자등록 상태(data.go.kr 15081808)를 사업자등록번호(b_no)로 조회합니다. 한 번에 100건까지 넣을 수 있습니다. 별도 연동 없이 사용할 수 있습니다. 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소진 요청 처리 시 XBOSS 작업을 생성하고 처리 결과를 저장합니다. 기관 원본의 조회 여부와 별개로 이 호출은 순수 읽기 전용이 아닙니다. 기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "b_no": "<b_no>"
    },
    "name": "opendata__nts__status"
  }
}

Input Schema

NameRequiredDescriptionDefault
b_noYes사업자등록번호 목록 - 각 10자리 숫자(예: ["1248100998"]). 최대 100건.
output_formatsNo선택 입력입니다. 결과를 엑셀(xlsx) 파일로도 받으려면 입력해 주세요. 파일은 결과의 artifacts[] 에 실립니다. 비워 두면 데이터만 받습니다.
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, and the description reinforces rather than contradicts them by explicitly warning that the call is '순수 읽기 전용이 아닙니다' because it creates an XBOSS job and stores a result. It adds real non-schema facts: one token consumed per call, 15-minute download URLs, 7-day file retention, and that a lost recovery_receipt cannot be repaired by signing up. Only the return payload content is left unexplained.

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 purpose is correctly front-loaded in the first three sentences, but the remainder is a dense, unbroken block of cross-cutting artifact, receipt, and idempotency boilerplate that reads as pasted-in policy text. Most clauses are individually informative, but the lack of any structural separation for a simple two-parameter lookup makes it harder to scan than it needs to be.

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 no output schema, the description does cover artifacts, retention windows, recovery paths, cost, and idempotency semantics, which is strong for a 3-parameter tool. The one remaining gap is that it never says what the returned business-status records actually contain (e.g. status code, tax type), leaving the agent to discover the response shape empirically.

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 3 already carry descriptions; the baseline would be 3. The description goes beyond the schema for request_idempotency_key, explaining that it must be generated before the first request, reused only with identical arguments to recover a lost response, and replaced for a new execution, plus that it is unavailable to anonymous calls.

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 opening sentence names a specific verb and resource ('국세청 사업자등록 상태 ... 조회') and cites the source dataset (data.go.kr 15081808), so an agent knows exactly what is being fetched. It does not, however, differentiate itself from the sibling opendata__nts__validate, which an agent could easily confuse with a status/validity lookup.

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 gives useful operational guidance for edge cases: request Excel via output_formats, call xdata__job__result if a download link expired, and reuse request_idempotency_key only to recover a lost response. It never states when to prefer this over opendata__nts__validate or when not to use it, so selection between sibling lookups is left 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