Skip to main content
Glama
opendata-kr

narajangteo-opening

by opendata-kr

낙찰 결과 검색

search_awards
Read-only

Search public procurement award winners by keyword, institution, region, industry, price range, business number, or date. Get contractor name and award amount.

Instructions

나라장터 낙찰 결과(최종낙찰자)를 공고명·기관·수요기관(코드)·지역·업종·추정가·사업자번호·기간으로 검색한다. '누가 얼마에 낙찰받았나', 경쟁사(bizno) 낙찰 이력, 되풀이 사업의 종단 조회에 쓴다. 특정 공고의 개찰·투찰업체·예비가 상세는 get_bid_result, 개찰 진행·유찰 발굴은 search_openings를 쓴다. 업무구분 미지정 시 물품/공사/용역/외자를 병렬 조회한다(API 요청이 업무구분 수 × 기간창 수 × 페이지 수로 늘어나므로 구분·기간을 좁혀 트래픽을 아낀다). 낙찰자만 반환하며 그 업체가 참여했으나 진 입찰은 미포함.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
biznoNo업체 사업자번호. 그 업체의 낙찰건만 조회(진 입찰은 미포함)
regionNo참가제한지역명(prtcptLmtRgnNm)
bidKindNo업무구분 배열(cnstwk=공사·servc=용역·thng=물품·frgcpt=외자). 미지정 시 전 구분 병렬 조회로 API 요청이 4배로 늘어난다. 업무구분을 알면 지정해 인증키 일일 트래픽을 아낀다
endDateNo조회 종료일 YYYYMMDD
keywordNo공고명 부분검색(bidNtceNm)
dateTypeNo날짜 기준. posted=공고게시(기본), opened=개찰
industryNo업종명(indstrytyNm)
maxPagesNo창당 최대 페이지(기본 10)
maxPriceNo추정가격 상한(presmptPrceEnd)
minPriceNo추정가격 하한(presmptPrceBgn)
pageSizeNo창당 페이지 크기(기본 100)
startDateNo조회 시작일 YYYYMMDD
institutionNo공고기관명(ntceInsttNm)
demandInstitutionNo수요기관명(dminsttNm)
detailProductCodeNo세부품명번호(dtilPrdctClsfcNo)
demandInstitutionCodeNo수요기관코드(dminsttCd). 종단 식별에 안정적
Behavior5/5

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

Annotations declare readOnlyHint and openWorldHint; description adds that only winning bidder is returned and excludes lost bids. Warns about API request multiplication when bidKind is unspecified. No contradictions with annotations.

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?

Description is several sentences long but each sentence adds value. Front-loaded with purpose and key behavior. Could be slightly more concise, but no unnecessary content.

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?

Given 16 parameters and no output schema, description covers return content (only winning bidder), usage optimization, and sibling differentiation. Lacks explicit return format but sufficient for typical use cases. Minor gap in fully describing output structure.

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% with detailed descriptions. Description reinforces key parameters (bidKind, region) with contextual usage advice, such as the impact of bidKind on API traffic. Adds value beyond schema but schema already does heavy lifting.

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?

Describes specific verb '검색한다' (searches) and resource '나라장터 낙찰 결과' (award results). Explicitly distinguishes from siblings by naming get_bid_result and search_openings with their different purposes. Purpose is clear and specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit use cases (who won, competitor history, longitudinal studies) and when not to use (for detailed bid results or opening progress, use alternatives). Gives performance advice on narrowing bidKind and date range to reduce API traffic.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/opendata-kr/narajangteo-opening-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server