XBOSS

나라장터 부정당업자 제재 조회

opendata__g2b__sanction

공공데이터포털에 개방된 나라장터 부정당업자 제재 정보(data.go.kr 15129466)를 사업자등록번호(bizno)로 조회합니다. 결과가 비어 있으면 이번 조회에서 해당 기록을 찾지 못한 것이고, 제재를 받은 적이 없다는 확인서는 아닙니다. 별도 연동 없이 사용할 수 있습니다. 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": {
      "bizno": "<bizno>"
    },
    "name": "opendata__g2b__sanction"
  }
}

Input Schema

Name	Required	Description
`bizno`	Yes	사업자등록번호 10자리(예: "1248100998"). 하이픈은 서버가 지운다.
`pageNo`	No	페이지 번호(기본 1).
`numOfRows`	No	페이지당 행 수(기본 100, 최대 100).
`inqryBgnDt`	No	조회 시작 일시 YYYYMMDDHHMM(선택).
`inqryEndDt`	No	조회 종료 일시 YYYYMMDDHHMM(선택).
`request_idempotency_key`	No	Optional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false, and the description explains WHY: each call consumes one token, creates an XBOSS task and stores the result, and is explicitly 'not purely read-only.' That is real context beyond the annotation flags. It also warns that the provider-side lookup and the tool's own side effects are independent. Minor gap: no mention of rate limits or failure modes.

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: purpose first, then the critical empty-result caveat. The remainder is bloated and inconsistently bilingual, with the idempotency paragraph restating the same rule ('Without it, calling again remains a new request') and an awkward '호출마다 토큰 1소진' fragment that is hard to parse. It is serviceable but not tight.

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?

For a 6-parameter query tool with a 100% documented schema and no output schema, the description covers purpose, result interpretation, per-call cost, non-read-only behavior, and idempotency recovery. Remaining omission is what fields the sanction records actually contain, which an agent would want before promising an answer to a user.

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

Parameters5/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 adds genuine semantics for the one parameter the schema defers to it: request_idempotency_key should be generated before the first request, reused only to recover a single lost response with identical arguments, and never reused for a new execution. That is exactly the guidance the schema description ('see the tool description') points to, so the description earns above baseline.

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 (조회 of 나라장터 부정당업자 제재 정보) plus the exact dataset identifier (data.go.kr 15129466) and the lookup key (bizno). An agent can immediately tell this is a business-registration-number lookup against government sanction records, distinct in subject matter from the sibling sanction lookups (env, kiscon) even without them being named.

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?

Implies usage context by saying the tool works without separate integration and that an empty result means 'not found in this query' rather than 'no sanctions on record' — a genuinely useful interpretation rule. However, it never states when to choose this over alternative sanction sources or what prerequisites (e.g. valid 10-digit bizno) gate a successful call.

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?