Skip to main content
Glama
korea-opendata-mcp

korea-opendata-mcp

by myungwoon

Search Festivals

search_festivals
Read-onlyIdempotent

Search nationwide Korean festivals, performances, and events by date range to find activities happening during a specific period.

Instructions

기간으로 전국 축제·공연·행사를 검색합니다.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
end_dateNo이 날짜까지 시작하는 행사. 기본: 시작일+30일
per_pageNo
start_dateNo이 날짜 이후 시작/진행 중인 행사. 기본: 오늘

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare this as read-only, idempotent, open-world, and non-destructive, so the safety profile is covered. The description adds that results span festivals, performances, and events nationwide, but it does not disclose pagination behavior, rate limits, or other operational context.

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?

The description is a single front-loaded sentence with no wasted wording. It is efficient, though its extreme brevity leaves important details to the schema and 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?

An output schema and rich annotations reduce the description's burden, and the core purpose is stated. However, for a four-parameter search tool with only 50% schema coverage, the description should still clarify pagination and parameter usage, which it does not.

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

Parameters2/5

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

Schema coverage is only 50%: the date fields are described in the schema, but page and per_page are not documented in either the schema or the description. The description's '기간으로' only restates the date-filtering role already conveyed by the schema, so it does not compensate for the undocumented parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb-resource pair: searching nationwide festivals, performances, and events by period. It clearly distinguishes this tool from the weather, subway, and statistic siblings by domain, so an agent can identify its purpose without opening the schema.

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 phrase '기간으로' implies that this tool should be used for date-range searches, but the description gives no explicit when-to-use or when-not-to-use guidance, and it names no alternative. The usage is understandable but relies on inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.