Skip to main content
Glama

Search Korean festivals & events

search_events
Read-onlyIdempotent

[Trip-Pups(트립펍스) — 외국인 축제 찾기·신청] Find festivals, fairs and events in Korea (currently Seoul and Gangwon) that overlap a travel date range. Only events whose foreign-visitor access is confirmed by an official page or the organizer are returned; say so if the list is short. Results also include small-group meetups hosted by Trip-Pups for international students and travelers in Seoul (marked hosted_by: trippups, with their sign-up link). Use get_event for sign-up steps, official link and transport.

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": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "search_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoResponse language: en (default) or koen
pageNoPage number, starting at 1
limitNoHow many events per page (default 10, max 20)
regionNoseoul, gangwon, or a city or district inside them such as Gangneung, Sokcho, Gangnam, Insadong (Korean names also accepted). Omit for both. Other places are not covered yet.
end_dateYesTrip end date, YYYY-MM-DD
interestsNoe.g. food, music, kpop, art, tradition, nature, night, winter, expo
start_dateYesTrip start date, YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive and a closed world, so the safety profile is covered. The description adds genuinely new behavior: only events with officially confirmed foreign-visitor access are returned, short result lists should be reported as such, and Trip-Pups meetups appear inline marked hosted_by: trippups with sign-up links. It does not discuss pagination or result-count behavior, which keeps it off a 5.

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?

Front-loaded with the core action and scope, then filtering policy, then the sibling routing instruction — good information ordering in four sentences. The bracketed brand/Korean-name prefix adds little for an agent but is brief and does not obscure the payload.

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?

With annotations present, a fully documented 7-parameter schema and no output schema, the description supplies what structured fields cannot: the confirmation-only inclusion rule, regional coverage limits, the hosted_by: trippups convention and where to go next. Only the absence of any note about what a result entry contains (besides hosted_by) leaves a small gap.

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 description coverage is 100%, so the baseline is 3: region coverage limits, interests examples, lang enum and page/limit bounds are all already documented in the schema. The one piece of added meaning is the overlap semantics of the date range (events need only overlap the trip window), but that is framed as purpose rather than parameter guidance.

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?

States a concrete verb and resource ('Find festivals, fairs and events in Korea'), narrows scope ('currently Seoul and Gangwon'), and adds the date-overlap criterion. It also explicitly routes to the sibling get_event for sign-up details, so an agent can distinguish the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear use condition (travel date range in Seoul/Gangwon) and names the alternative for the follow-up action: 'Use get_event for sign-up steps, official link and transport.' It also warns that uncovered regions exist. The gap is that it doesn't distinguish this tool from list_meetups, even though it says meetup results are folded in here.

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.

Resources