Skip to main content
Glama

GRNT — Korean Grant & Subsidy Intelligence

제도 상세(원문 요약)

get_subsidy_detail
Read-only

제도 1건의 목적·지원대상·선정기준 원문·지원내용·신청방법·신청기한·구비서류·문의처·온라인 신청 링크를 반환합니다. 프로필을 함께 주면 판정도 붙습니다.

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": {
      "service_id": "<service_id>"
    },
    "name": "get_subsidy_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNo판정에 쓰는 사용자 조건. 없는 항목은 '모름'으로 보고 판정하지 않습니다. 개인은 나이·지역·소득·상황, 창업·기업은 business 블록(예비/운영, 업력, 업종)을 씁니다.
service_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds real value by disclosing that supplying a profile appends an eligibility judgment, but says nothing about error behavior for an unknown service_id or whether the judgment result is embedded or separate.

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 returned content and closed with the optional profile behavior. The field enumeration is long but each item conveys what data is available, so it earns its space; no filler or repetition.

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 carries the return-shape burden well by listing the returned fields. Combined with the richly documented nested profile schema, it is nearly complete, with only the source/semantics of service_id and the shape of the judgment output left open.

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?

The nested profile object is thoroughly documented in the schema, but service_id has no schema description at all (50% coverage). The description compensates partly by framing the call as 'one 제도' and by explaining that profile is optional and triggers a judgment, yet it never explains what service_id is or how to obtain a valid one.

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 concrete verb and resource ('제도 1건의 … 반환합니다') and enumerates exactly what the record contains: purpose, target, selection criteria, support content, application method, deadline, documents, contact, and online link. It reads clearly as a single-record detail lookup, implicitly distinct from search/list siblings, though it never names an alternative.

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?

Usage is only implied: fetch one program by service_id, optionally attach a profile to get a judgment. There is no explicit statement of when to prefer this over check_eligibility or search_subsidies, nor any prerequisite such as where service_id comes from.

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.