Skip to main content
Glama
socialkim

korea-onegov-mcp

by socialkim

마감임박 지원사업 공고

onegov_deadline_grants
Read-onlyIdempotent

Retrieve government grants and support announcements sorted by impending deadlines. Filter by max days until deadline, organization name, and result count.

Instructions

접수 마감이 임박한 정부 지원사업·공고를 마감일 순으로 돌려준다. 창업·중소기업·소상공인 지원사업 탐색의 출발점.

Args:

  • max_dday (number, 0~60, 선택): D-day 상한. 예: 7 이면 일주일 안에 마감하는 것만.

  • org_contains (string, 선택): 기관명 부분 문자열 필터(예: "중소벤처기업부", "조달청").

  • limit (number, 1~100, 기본 30)

  • response_format ('markdown'|'json', 기본 markdown)

Returns: { grants: [{ id, title, org, ministry_name, deadline_at, dday, support_field, apply_target, region, startup_years, source_url, kogl_type }] } dday=0 은 오늘 마감이라는 뜻이다.

Examples:

  • "이번 주 마감인 지원사업" → max_dday=7

  • "중기부 지원사업 마감 임박" → org_contains="중소벤처기업부"

  • 조건에 맞는 게 없으면 onegov_find_support_programs 로 넓게 검색할 것.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo최대 건수
max_ddayNoD-day 상한(일)
org_containsNo기관명 부분 문자열 필터
response_formatNo출력 형식. 'markdown'은 사람이 읽기 좋은 요약(기본값), 'json'은 API 원본에 가까운 구조화 데이터.markdown
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds context like dday=0 meaning today's deadline and explains the return object structure, but the behavioral core is well-covered by annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Concisely structured with Korean overview, clear Args/Returns/Examples sections. Every sentence adds value, no redundancy. The length is appropriate for the complexity.

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?

Despite no output schema, the description fully documents the returned fields including meaning of dday, and provides fallback guidance. All necessary context for using the tool correctly is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with basic descriptions, but the description adds rich semantics: examples for max_dday and org_contains, explanation of limit default and response_format options, and interpretation of dday in the return object. This goes beyond the schema.

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?

The description clearly states the tool returns government support projects with imminent deadlines sorted by deadline (마감일 순), and specifies target users (창업·중소기업·소상공인). This distinguishes it from siblings like onegov_find_support_programs which is for broader searches.

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?

The description provides explicit examples for common use cases (e.g., max_dday=7 for this week's deadlines, org_contains for specific ministries) and explicitly advises using onegov_find_support_programs if no matches, giving clear when-to/alternative guidance.

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/socialkim/korea-onegov-mcp'

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