Skip to main content
Glama

BOIM Korea Vendor Directory

by io.boim
OverviewDiscussionsAdmin

진행 중인 공공기관 입찰 공고(나라장터·국방·LH·수자원·누리장터) 찾기 — 모든 분야

find_public_bids
Read-onlyIdempotent

[보임 — 한국 업체·입찰 공고 찾기] 나라장터(조달청)·국방전자조달·LH·한국수자원공사·누리장터(조달청 민간입찰)의 마감 전 입찰 공고를 모든 분야에서 찾습니다. 모든 공고를 같은 기준으로 나눕니다 — 분야(group) = 물품분류 대분류(물품)·공공조달분류 대분류(용역)·주공종(공사), 나라장터 밖 기관 공고는 "<종류>(분류 없음)". 결과의 type이 물품/용역/공사, origin이 공고한 곳입니다. 공공데이터포털의 다섯 기관 입찰공고 데이터로 하루 두 번 갱신하며 마감이 가까운 순서입니다. 공공기관 일감을 찾는 업체, 또는 어떤 기관이 무엇을 사려는지 물을 때 쓰세요. 결과마다 원문 링크(url)와, 있으면 추정가격이 있습니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNo물품·용역·공사·기타 중 하나(비우면 모두)
limitNo
queryNo공고명·수요기관에 들어간 말
regionNo수요기관 시·도(예: 서울, 경북). 중앙기관·공사는 지역이 없을 수 있습니다. 비우면 전국
categoryNo분야·품명 낱말(예: 안내판, 간판, 인쇄, 건축공사업, 전기공사업, 학술연구, 컴퓨터, 소프트웨어, 청소)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"품명 또는 분야(예: 안내판, 간판, 현수막, 전광판, 인쇄, 교통안전시설)"New value: +"분야·품명 낱말(예: 안내판, 간판, 인쇄, 건축공사업, 전기공사업, 학술연구, 컴퓨터, 소프트웨어, 청소)"
    • addedInput schema / properties / type
      Added value: +{
+  "description": "물품·용역·공사·기타 중 하나(비우면 모두)",
+  "type": "string"
+}
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds genuine behavior beyond that: twice-daily refresh from 공공데이터포털, deadline-ascending ordering, and that each result carries an original url and estimated price when available.

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?

Front-loaded with scope and sources, and each subsequent clause (classification rule, refresh cadence, sort order, output fields, intended users) carries distinct information. It is dense and long for a search tool, but nothing is clearly redundant.

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?

No output schema exists, and the description compensates well by describing return fields (url, estimated price, type, origin) and sort order. The `limit` parameter and any pagination behavior remain unexplained, a minor gap for an otherwise complete definition.

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 80%, so the baseline is 3. The description clarifies the meaning of the classification scheme behind `category`/`type` (대분류 mapping, type/origin in results) but adds no syntax or format detail, and the undocumented `limit` parameter (the missing coverage) is left unaddressed.

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 (찾습니다/find) and resource (마감 전 입찰 공고) plus exact scope: five named sources (나라장터·국방전자조달·LH·수자원·누리장터) and all fields. It also explains how results are classified (group/type/origin), so an agent can immediately tell this apart from the business/shop/vendor siblings.

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?

Gives concrete when-to-use scenarios — a company seeking public-institution work, or asking what an institution intends to buy. However it names no alternatives or exclusions, so it does not route the agent away from siblings like find_businesses or search_vendors.

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

All BOIM Korea Vendor Directory 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