Skip to main content
Glama
opendata-kr

narajangteo-opening

by opendata-kr

개찰결과 검색

search_openings
Read-only

Search Korean public procurement opening results and filter by status (open completed, no bid, re-bid) to discover no-bid or re-bid notices.

Instructions

나라장터 개찰결과 목록을 검색하고 진행상태(개찰완료/유찰/재입찰)로 필터한다. 유찰·재입찰 공고 발굴에 쓴다. 최종낙찰자 검색은 search_awards, 단일 공고 상세는 get_bid_result를 쓴다. status는 API가 아니라 응답 기준 클라이언트 필터라 응답이 느리니 기관·업종·기간으로 좁혀 쓴다(truncated=true면 미완 스캔). 업무구분 미지정 시 전 구분 병렬 조회로 API 요청이 업무구분 수 × 기간창 수 × 페이지 수로 늘어난다(구분·기간을 좁혀 트래픽 절약). 재입찰은 동일 공고 내 재입찰이며 재공고가 아니다(재공고는 입찰공고 서비스 소관).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionNo참가제한지역명(prtcptLmtRgnNm, 예: 인천광역시)
statusNo진행상태 필터(응답 progrsDivCdNm 기준 클라이언트 필터)
bidKindNo업무구분 배열(cnstwk=공사·servc=용역·thng=물품·frgcpt=외자). 미지정 시 전 구분 병렬 조회로 API 요청이 4배로 늘어난다. 업무구분을 알면 지정해 인증키 일일 트래픽을 아낀다
endDateNo조회 종료일 YYYYMMDD (startDate와 함께 지정)
keywordNo공고명(bidNtceNm)
dateTypeNo날짜 기준: posted=공고게시(기본), opened=개찰
industryNo업종명(indstrytyNm)
maxPagesNo창당 최대 페이지(기본 5)
pageSizeNo창당 페이지 크기(기본 20, 개찰결과는 느려 작게 권장)
startDateNo조회 시작일 YYYYMMDD (endDate와 함께 지정)
institutionNo공고기관명
demandInstitutionNo수요기관명(dminsttNm)
Behavior5/5

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

Adds significant context beyond annotations: status is client-side filter, response speed, truncated flag meaning, parallel queries with unspecified bidKind, distinction between 재입찰 and 재공고. No contradiction 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 informative but slightly lengthy; however, every sentence adds value. Front-loaded with purpose and usage, then details.

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, but description covers behavior like truncation, parallelism, and response speed. Could mention return format but sufficient for correct use.

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 description coverage is 100%, so baseline 3. Description adds value by explaining performance implications of bidKind and the client-side nature of status filter.

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?

Description clearly states it searches 나라장터 개찰결과 목록 and filters by status. It differentiates from siblings search_awards (final awardee) and get_bid_result (single notice).

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?

Explicitly states when to use (finding 유찰·재입찰 notices), when not (use siblings), and provides performance tips: narrow by institution/industry/period, specify bidKind to reduce 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