Skip to main content
Glama

BOIM Korea Vendor Directory

업체 카드 조회

get_vendor
Read-onlyIdempotent

Get one vendor card by id: records and amounts by product, main buyer agencies and regions, contract types, unit-price range, certifications, sources and update date. [보임 — 한국 업체·입찰 공고 찾기] search_vendors가 돌려준 id로 업체 카드 전체(품명별 1년 실적·금액·계약 품목, 주요 납품 기관·지역, 계약 방법, 조달청 계약 단가 범위, 인증, 공급 지역, 출처, 갱신일, 데이터 한계)를 가져옵니다.

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": {
      "id": "<id>"
    },
    "name": "get_vendor"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes업체 id(search_vendors 결과의 id)

Output Schema

NameRequiredDescriptionDefault
idNo업체 id
urlNo업체 카드 주소
citeNo출처 한 줄
nameNo상호
certsNo인증
errorNo실패 사유(isError일 때만)
readyNoAI 준비도 점수
checksNo확인 근거
groupsNo분야
limitsNo데이터 한계
claimedNo업체가 직접 등록했는지
similarNo같은 주력 품명 업체(순위 아님)
sourcesNo출처
updatedNo자료 갱신일
hq_regionNo본사 지역
categoriesNo품명별 실적
procurementNo조달 실적(품명·금액·기관·계약 방법)
price_rangesNo조달청 계약 단가 범위
supply_regionsNo공급 지역
business_statusNo국세청 사업자 상태와 확인일

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "business_status": {
      +      "description": "국세청 사업자 상태와 확인일"
      +    },
      +    "categories": {
      +      "description": "품명별 실적"
      +    },
      +    "certs": {
      +      "description": "인증"
      +    },
      +    "checks": {
      +      "description": "확인 근거"
      +    },
      +    "cite": {
      +      "description": "출처 한 줄"
      +    },
      +    "claimed": {
      +      "description": "업체가 직접 등록했는지"
      +    },
      +    "error": {
      +      "description": "실패 사유(isError일 때만)"
      +    },
      +    "groups": {
      +      "description": "분야"
      +    },
      +    "hq_region": {
      +      "description": "본사 지역"
      +    },
      +    "id": {
      +      "description": "업체 id"
      +    },
      +    "limits": {
      +      "description": "데이터 한계"
      +    },
      +    "name": {
      +      "description": "상호"
      +    },
      +    "price_ranges": {
      +      "description": "조달청 계약 단가 범위"
      +    },
      +    "procurement": {
      +      "description": "조달 실적(품명·금액·기관·계약 방법)"
      +    },
      +    "ready": {
      +      "description": "AI 준비도 점수"
      +    },
      +    "similar": {
      +      "description": "같은 주력 품명 업체(순위 아님)"
      +    },
      +    "sources": {
      +      "description": "출처"
      +    },
      +    "supply_regions": {
      +      "description": "공급 지역"
      +    },
      +    "updated": {
      +      "description": "자료 갱신일"
      +    },
      +    "url": {
      +      "description": "업체 카드 주소"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety behavior is covered. The description adds useful scope beyond annotations by listing the returned card fields and mentioning '데이터 한계' (data limitations), though it does not detail those limitations.

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?

The English sentence is front-loaded and efficient, and the Korean restatement adds some extra detail such as supply regions and data limitations. There is minor redundancy from the bilingual duplication, but the description remains appropriately sized.

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

Completeness5/5

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

The tool has one required parameter, full schema coverage, rich read-only annotations, and an output schema. The description supplies the key source of the id and summarizes the card contents, so an agent has enough information to invoke it correctly.

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 description coverage is 100%, and the schema already documents the single 'id' parameter as the id from search_vendors results. The description repeats that same semantic without adding new syntax, format, or validation details.

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: 'Get one vendor card by id', then enumerates the card contents. It also distinguishes the tool from search_vendors by noting that this fetches the full card using an id returned by search_vendors.

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?

The description clearly ties usage to an id returned by search_vendors, giving the agent the key prerequisite. However, it does not explicitly state when not to use this tool or compare it against the other sibling lookup tools.

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.