Skip to main content
Glama

GRNT — Korean Grant & Subsidy Intelligence

제도 1건 정밀 판정

check_eligibility
Read-only

제도ID(service_id)와 프로필로 한 제도의 자격을 정밀 판정합니다. 어긋난 항목·필요한 추가 정보·선정기준 원문·문의처를 함께 반환합니다.

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>",
      "profile": "<profile>"
    },
    "name": "check_eligibility"
  }
}

Input Schema

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

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?

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered and the description's contribution is the return payload: mismatched items, needed extra information, raw selection criteria, and contact details. That is useful context beyond the annotations, but it says nothing about how partial profiles degrade the verdict (only the schema mentions 'unknown' handling) or about limits and failure 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 short sentences with the input pair first and the returned payload second, so nothing is wasted and the most decision-relevant information is front-loaded. Minor deduction because the return list is compressed into a single dense clause.

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?

The tool is a complex judgment over a deeply nested profile and has no output schema, so the description must convey return values; it does so at a high level with four named components. It leaves the meaning of each returned component and the effect of missing profile fields to the schema, which is a small but real gap for a tool of this complexity.

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 100%, so both top-level parameters and the nested profile fields are already fully documented in the schema, including the meaning of the business block, situations, and income_percent. The description only restates that service_id and a profile are the inputs and adds no format or semantics beyond that, which is the baseline 3 case.

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 (정밀 판정, precise determination) and a specific resource (one program's eligibility via 제도ID/service_id plus a profile), so the agent knows it is a per-program eligibility evaluator rather than a search tool. It does not explicitly distinguish itself from get_subsidy_detail or get_service_meta, so the sibling differentiation is only implicit.

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 description is framed as operating on one program ID and a profile, which implies the natural workflow of searching first and then judging a single result, but it never states when to use this instead of the detail or meta lookups. There are no exclusions, prerequisites, or alternative-tool routing.

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.