Skip to main content
Glama

GRNT — Korean Grant & Subsidy Intelligence

마감 임박 지원금 캘린더

deadline_calendar
Read-only

앞으로 N일(기본 30일) 안에 마감되는 지원금·창업지원사업을 날짜별로 보여 줍니다. 두 트랙(개인·창업)을 함께 또는 따로 볼 수 있고, 마감일을 확실히 읽은 것만 넣으며 '상시신청·예산 소진 시'처럼 날짜가 없는 건수도 함께 알립니다.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "deadline_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
sidoNo지역으로 좁힐 때(예: 인천광역시)
limitNo
trackNoall
keywordNo제도명 키워드
sigunguNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the description's added context is the real contribution: it discloses a data-confidence filter (only entries whose deadline was clearly parsed are included) and that undated entries ('상시신청·예산 소진 시') are reported as a count rather than listed. That tells the agent why the calendar may be incomplete without implying an error. It doesn't disclose ordering or the 50/200 limit truncation behavior.

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?

Two sentences, front-loaded with the core behavior and the default window before the track and data-caveat details. Dense in Korean but every clause carries information; no filler or restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only query tool with no output schema, the description conveys the main result shape (date-grouped list plus an undated count) adequately. It omits how limit/pagination affects results (default 50, max 200) and leaves sigungu undefined, so an agent could unknowingly request a truncated or malformed region filter.

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 only 33%, so the description must compensate, and it partly does: it explains days (N, default 30) and the two-valued track semantics (함께 또는 따로 = all/personal/business). It adds nothing for limit or sigungu, the latter being undocumented in both schema and description, which is a genuine gap for a 6-parameter tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific behavior: it shows 지원금·창업지원사업 that close within N days (default 30), grouped by date, with a personal/business track split. An agent can distinguish this deadline-oriented view from siblings like search_subsidies or list_region_subsidies without opening a schema. It stops short of naming the alternative it replaces.

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

Usage Guidelines3/5

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

The 'closing soon within N days' framing implies a deadline-driven discovery scenario, which is usable guidance. However, there is no explicit when-to-use vs. when-not statement and no sibling is named as an alternative, so the routing decision is left to inference.

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.