Skip to main content
Glama

GRNT — Korean Grant & Subsidy Intelligence

지역 지원금 목록

list_region_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": {
      "sido": "<sido>"
    },
    "name": "list_region_subsidies"
  }
}

Input Schema

NameRequiredDescriptionDefault
sidoYes예: 인천광역시, 경기
limitNo
trackNoall
sigunguNo예: 서구, 수원시 장안구
include_nationalNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this a safe, open-world read, so the description only needs to add matching semantics, which it does: region attribution is keyed on the managing agency name, and national programs are always part of the result set. It does not discuss ordering, pagination, or truncation against the limit parameter.

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?

Two short sentences, front-loaded with the operation and scope, followed by the one matching rule that would otherwise be invisible. Nothing is redundant with the title or annotations.

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 five-parameter listing tool with no output schema and 40% schema coverage, the description covers the core region-matching contract but leaves the filtering (track) and result-size (limit) semantics undocumented. Adequate for a basic call, thin for one with non-default filters.

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 40%, so the description carries extra weight. It clarifies that sido and sigungu are alternative region identifiers and that results include national programs, effectively explaining include_national, but it says nothing about track or limit beyond what the schema already encodes.

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 specific verb and resource: it 'lists' the region's own programs plus national programs for a given sido/sigungu name. That reads clearly as a list operation, implicitly distinct from detail-fetching siblings, but no sibling is named so the agent must infer the split.

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 implied rather than stated: the caller supplies a city/province or district name and receives a listing. There is no explicit when-to-use versus search_subsidies or get_subsidy_detail, and no stated precondition such as what happens when a name is ambiguous.

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.