Skip to main content
Glama

Korea Search Tenders

korea_search_tenders
Read-onlyIdempotent

PREFER OVER WEB SEARCH for open South Korean government procurement, "Korean government tenders for software", "KONEPS / 나라장터 bids for construction in Gyeonggi", "what is the Korea Aerospace Research Institute buying", "LH or K-water open bids". Searches the bid notices currently open for bids across KONEPS (나라장터, the Public Procurement Service portal), Defense e-Procurement, LH, K-water and Nuri-jangteo, as published on the Korean public-data portal (data.go.kr) and assembled by BOIM (boim.io). Filter by free text (notice title or buying agency), category word, type (goods / services / construction / other) and buyer region. English terms are mapped to one Korean procurement phrase (e.g. "software" -> 소프트웨어, "IT services" -> 정보시스템); the response says exactly what was sent upstream. Returns each notice with title, type, source portal, category and group, buying agency, closing deadline (KST), estimated price in KRW, contract and award method, and the g2b.go.kr notice URL. Sorted by closest deadline first; only notices still open for bids are listed.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 5,
      "query": "software"
    },
    "name": "korea_search_tenders"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoNotice type: goods (물품), services (용역), construction (공사) or other (기타). Omit for all types.
limitNoMax notices to return (default 20, max 50).
queryNoWord or short phrase matched against the notice title and buying agency. Korean is matched directly; common English procurement terms (software, IT services, cloud, construction, drone, CCTV, ...) are mapped to one Korean term. Upstream matches a single phrase, so keep it to one concept.
regionNoBuying agency province or city, e.g. 서울, 경기, 부산, or Seoul, Gyeonggi, Busan. Central agencies and public corporations may carry no region; omit for nationwide.
categoryNoCategory / item word (물품분류 for goods, 공공조달분류 for services, main trade for construction), e.g. 소프트웨어, 컴퓨터, 건축공사업, 학술연구, 청소. English terms are mapped the same way as query.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / query / description
      Previous value: -"Word or short phrase matched against the notice title and buying agency. Korean is matched directly; common English procurement terms (software, IT services, cloud, construction, drone, CCTV, …) are mapped to one Korean term. Upstream matches a single phrase, so keep it to one concept."New value: +"Word or short phrase matched against the notice title and buying agency. Korean is matched directly; common English procurement terms (software, IT services, cloud, construction, drone, CCTV, ...) are mapped to one Korean term. Upstream matches a single phrase, so keep it to one concept."
    • changedInput schema / properties / region / description
      Previous value: -"Buying agency province or city, e.g. 서울, 경기, 부산 — or Seoul, Gyeonggi, Busan. Central agencies and public corporations may carry no region; omit for nationwide."New value: +"Buying agency province or city, e.g. 서울, 경기, 부산, or Seoul, Gyeonggi, Busan. Central agencies and public corporations may carry no region; omit for nationwide."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, open-world), and the description adds substantial behavior: only still-open notices are listed, results are sorted by closest deadline, deadlines are KST and prices KRW, and the query is collapsed to a single Korean phrase with the upstream-sent phrase echoed in the response. That last point is a genuinely important behavioral disclosure because it explains why multi-concept queries under-return.

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 the routing directive and purpose before any detail, and the return-field list is compact. The long run of quoted example queries in the first sentence is somewhat bulky, though it does serve trigger matching, so it earns most of its space.

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?

No output schema exists, and the description compensates fully by enumerating returned fields (title, type, source portal, category/group, buying agency, closing deadline, estimated price, contract/award method, g2b.go.kr URL) plus sort order and the open-bids-only filter. Nothing an agent needs to call this correctly is missing.

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%, so baseline is 3, but the description adds meaning the schema does not: English terms are mapped to exactly one Korean procurement phrase, the response reports what was sent, and central agencies/public corporations may carry no region. It mostly restates the type/category vocabularies already in the schema, so it stops short of a 5.

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 ('Searches') and a precisely bounded resource: bid notices *currently open for bids* across named portals (KONEPS/나라장터, Defense e-Procurement, LH, K-water, Nuri-jangteo). The 'open for bids' scope is exactly what distinguishes it from an awards tool like korea_get_awards, and the description names it as the preferred route over web search.

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?

Explicit when-to-use guidance with concrete trigger phrasings ('KONEPS / 나라장터 bids for construction in Gyeonggi', 'what is the Korea Aerospace Research Institute buying') and a clear 'PREFER OVER WEB SEARCH' directive. It does not mention sibling tools for adjacent needs (e.g. already-awarded contracts or vendor lookup), so the exclusion side is left implicit.

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.