Skip to main content
Glama

GRNT — Korean Grant & Subsidy Intelligence

지원금 카탈로그 변화 비교

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

Input Schema

NameRequiredDescriptionDefault
limitNo
to_dateNoYYYY-MM-DD (기본: 최신)
from_dateNoYYYY-MM-DD (비교 기준일)
service_idNo한 제도만 볼 때

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds real behavioral substance beyond that: which fields are diffed (period/amount/target/recruitment status) and the default comparison pair. It does not say what happens when fewer than two snapshots exist for the requested window, which is the main behavioral edge case for a diff tool.

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 sentences with zero filler: the first states the operation and its output categories, the second states the default fallback. Both are front-loaded and every clause carries information an agent needs.

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?

For a read-only comparison tool with no output schema and four optional parameters, the description does the important work: it describes the shape of the result in terms of added/removed/changed categories and explains the zero-argument default. The remaining gaps (limit semantics, insufficient-snapshot behavior) are modest rather than disqualifying.

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 75% — to_date, from_date, and service_id are documented in the schema, while limit carries only default/min/max with no stated meaning. The description contributes the interaction rule between from_date and to_date (no dates = last two snapshots), but it says nothing about what limit constrains (number of change entries?) or how service_id behaves in a two-snapshot comparison.

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 (compare) and resource (two dated catalog snapshots/ledgers), and it enumerates exactly what the comparison surfaces: newly added programs, removed programs, and programs with changed period/amount/target/recruitment status. That is far more specific than a restatement of the name, though it never explicitly contrasts itself with siblings such as search_subsidies or get_subsidy_detail.

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 closing sentence supplies a genuine usage rule — omitting dates falls back to the two most recent snapshots — which tells the agent it can call with zero arguments. However, there is no explicit when-to-use versus when-not, and no pointer to an alternative when the agent wants current program data rather than a diff.

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.