Skip to main content
Glama

GRNT — Korean Grant & Subsidy Intelligence

내 조건 맞춤 지원금 찾기

search_subsidies
Read-only

나이·성별·거주지·소득구간·상황(임신·출산·무주택·구직·장애 등)과 사업자 조건(예비창업자/운영 중, 업력, 소상공인·중소기업, 업종)을 주면 정부·지자체 지원금과 창업·소상공인·기업 지원사업 후보를 '받을 가능성 높음 / 조건 확인 필요 / 정보 부족'으로 나눠 사유·금액·신청기한·문의처와 함께 돌려줍니다. 모르는 항목은 비워 두면 '정보 부족'으로 답하고 무엇을 더 물어야 하는지 알려 줍니다.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "profile": "<profile>"
    },
    "name": "search_subsidies"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNo청년·주거·창업·자금 등 주제 필터
limitNo
trackNo트랙 선택. business 면 창업·기업 공고만 봅니다.
keywordNo제도명·내용 키워드
profileYes판정에 쓰는 사용자 조건. 없는 항목은 '모름'으로 보고 판정하지 않습니다. 개인은 나이·지역·소득·상황, 창업·기업은 business 블록(예비/운영, 업력, 업종)을 씁니다.
include_closedNo모집 마감된 공고도 포함할지
include_ineligibleNo해당 없음까지 포함할지

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description goes further by disclosing the three-way classification of candidates and that each result carries reason, amount, deadline and contact. It also explains the failure mode for missing profile data (routed to 'insufficient info' plus follow-up questions), which is real behavioral insight. Rate limits, auth needs and result ordering/truncation from `limit` are not mentioned.

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, both doing work: the first enumerates inputs and the returned classification/output fields, the second handles the unknown-input case. Front-loaded and free of filler, though the long Korean clause chain makes the input enumeration dense on first read.

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?

With no output schema, the description correctly carries the return-value burden and does so, spelling out the three buckets and the per-item fields returned. For a 7-param tool with nested objects and enums this is nearly complete; only result ranking and how `limit`/pagination shape the response are left unaddressed.

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 description coverage is 86%, so the baseline is 3. The description does add interpretive meaning: individuals are judged on age/region/income/situations while startups and companies rely on the `business` block (pre/operating, years, industry). However, that restates what the nested `profile` schema already documents, so net gain beyond the schema is marginal.

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?

The description gives a precise verb+resource: it takes demographic and business conditions and returns government/local subsidy and startup support candidates, bucketed into 'high likelihood / needs verification / insufficient info' with reason, amount, deadline and contact. That is far more specific than the bare name. It does not explicitly contrast itself with siblings like check_eligibility or get_subsidy_detail, so the differentiation is implied by scope rather than stated.

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?

It gives clear operating guidance: what inputs to supply, and that unknown fields should be left blank so they are excluded from judgment with a prompt about what else to ask. It does not state when to prefer alternative tools (e.g., list_region_subsidies for a pure regional listing, or check_eligibility for a single-program verdict), leaving that 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.