Skip to main content
Glama

GRNT — Korean Grant & Subsidy Intelligence

서비스·데이터 상태

get_service_meta
Read-only

카탈로그 상태(실데이터/샘플), 판정 등급 정의, 자격 코드 목록, 입력 가능한 상황 태그, 개인정보 설계를 반환합니다.

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": "get_service_meta"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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, and openWorldHint=true, so the safety profile is covered externally. The description adds that the payload is reference/catalog material rather than live records, but says nothing about freshness, caching, whether the catalog status can change between calls, or any access requirements.

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?

A single front-loaded sentence enumerating the five returned content categories, with no filler or repetition. It is dense but readable, and nothing extraneous is included.

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?

With no output schema, the description carries the full burden of describing return values, and it does so only as a five-item list without structure or detail (e.g., what a passing grade or an eligibility code looks like). For a zero-parameter reference tool this is adequate but leaves the agent guessing at response shape.

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

Parameters4/5

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

The tool takes zero parameters and the schema is an empty object, so there is no parameter semantics to explain. The baseline of 4 applies; the description correctly makes no attempt to describe inputs.

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 names a specific verb (반환합니다) and enumerates the exact resource contents: catalog status (real vs. sample data), grade definitions, eligibility codes, situation tags, and privacy design. This clearly separates it from the sibling tools, which all operate on actual subsidy/ledger data rather than metadata. It falls short of 5 only because it never explicitly says it is the metadata/reference tool that should be consulted before the data tools.

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?

No explicit when-to-use or when-not-to-use statement is given; the guidance is only implied by the fact that the tool returns reference material (codes, tags, grade definitions) that the other tools likely consume. There is no mention of order of operations, prerequisites, or that this must be called before interpreting eligibility results.

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.