Skip to main content
Glama

부정당제재 업체 조회

debarred_company
Read-only

Check whether a Korean business registration number currently has active debarment sanctions in public procurement, with sanction details. 사업자등록번호로 조회 시점에 유효한 부정당제재 여부를 확인합니다. 만료·해제 이력은 제공하지 않으며, 제재가 없으면 no_active_sanctions 로 정상 응답합니다. 응답은 business_no·checked_at·status·count·sanctions(number·name·agency·start_date·end_date·basis) 입니다. [호출당 5포인트]

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": "debarred_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
biznoYes사업자등록번호 10자리 (하이픈 허용)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already say readOnlyHint=true and openWorldHint=true, so the safety profile is covered. Beyond that, the description reports the negative-result behavior (no_active_sanctions returned normally), the exact response fields, and a per-call cost of 5 points, which are useful behavioral details not found in the annotations. It does not cover error handling or auth.

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

Conciseness4/5

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

All content is useful: purpose, scope exclusion, negative case, response shape, and cost. It is front-loaded and readable. However, every sentence is duplicated in English and Korean, which makes it longer than necessary without adding information.

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?

Because there is no output schema, spelling out the response fields is essential, and the description does that fully. The negative-result case, sanction-history exclusion, and point cost are also covered. Only invalid-input behavior is left out.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and there is only one parameter, and the schema already documents the 10-digit format with hyphens allowed. The description only restates that lookup uses the business registration number, so it adds almost no new meaning beyond the schema. Baseline 3 applies.

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 gives a specific verb and resource: check whether a Korean business registration number currently has active debarment sanctions in public procurement. Mentions of '부정당제재' and 'in public procurement' also help separate this tool from general company or bid lookups. It never names or contrasts a sibling tool, so it doesn't reach the top score.

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?

'조회 시점에 유효한' sets the time scope of the check, and the description explicitly excludes expired or released sanction history, which functions as a when-not statement. However, it names no alternative tool for the excluded case, so the agent must work out for itself which sibling to use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.