Skip to main content
Glama

This Weekend (이번 주말)

행사 찾기

search_events
Read-onlyIdempotent

[이번 주말: 축제·공연·전시 찾기] 날짜, 지역, 검색어로 공개 행사를 찾습니다. 날짜를 비우면 이번 주말(한국 시간) 행사를 찾습니다. 남은 행사가 있으면 nextOffset을 offset에 넣어 이어서 받습니다. 검색어가 든 행사가 없으면 뜻이 비슷한 말로 한 번 더 찾고, 그때 쓴 말을 related에 적습니다.

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_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNo지역 이름. 시·도(서울, 부산)나 시·군·구(마포구, 전주시)를 넣습니다.
freeNotrue면 무료 행사만, false면 유료 행사만 찾습니다. 비우면 요금을 따지지 않습니다.
tagsNo이 태그가 모두 붙은 행사만 찾습니다. 태그는 행사 글에 적힌 말에서 읽은 것이라, 없으면 "아님"이 아니라 "모름"입니다. 쓸 수 있는 이름: kids, family, teens, adults, seniors, pets, indoor, outdoor, watch, hands-on, food, market, walk, run, learn, heritage, nature, science, lights, fireworks, books, seasonal, halloween, christmas, year-end, new-year, evening, free, partly-paid, paid, book-ahead, walk-in.
limitNo한 번에 받을 최대 개수. 1부터 50까지이고 기본값은 20입니다.
queryNo행사 이름, 장소, 분야, 주최에서 찾을 낱말.
offsetNo앞에서 건너뛸 개수. 이전 결과의 nextOffset을 넣으면 다음 묶음을 받습니다. 기본값은 0입니다.
endDateNo끝 날짜(YYYY-MM-DD). 비우면 시작 날짜 하루만 찾고, 시작 날짜도 비었으면 이번 주말 마지막 날까지 찾습니다.
startDateNo시작 날짜(YYYY-MM-DD). 비우면 이번 주말 첫날입니다.

Output Schema

NameRequiredDescriptionDefault
limitYes
rangeYes찾은 날짜 범위(한국 시간). endDate가 null이면 끝을 정하지 않은 것이고, includePast=1로 찾으면 range 자체가 null입니다.
totalYes조건에 맞는 행사 전체 개수.
eventsYes
offsetYes
relatedNo검색어가 든 행사가 없어서 뜻이 비슷한 말로 다시 찾았을 때만 붙습니다. events는 groups의 묶음마다 한 낱말 이상이 맞는 행사입니다.
coverageYes모아 둔 자료의 날짜 범위와 마지막 수집 시각. stale이 true면 저장소 대신 예비 사본에서 읽은 자료입니다.
returnedYes
nextOffsetYes다음 묶음을 받을 때 offset에 넣을 값. 남은 행사가 없으면 null입니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / offset / maximum
      Previous value: -5000New value: +20000
    • changedInput schema / properties / tags / description
      Previous value: -"이 태그가 모두 붙은 행사만 찾습니다. 태그는 행사 글에 적힌 말에서 읽은 것이라, 없으면 \"아님\"이 아니라 \"모름\"입니다. 쓸 수 있는 이름: kids, family, teens, adults, seniors, pets, indoor, outdoor, watch, hands-on, food, market, walk, learn, heritage, nature, science, lights, fireworks, books, seasonal, halloween, christmas, year-end, new-year, evening, free, partly-paid, paid, book-ahead, walk-in."New value: +"이 태그가 모두 붙은 행사만 찾습니다. 태그는 행사 글에 적힌 말에서 읽은 것이라, 없으면 \"아님\"이 아니라 \"모름\"입니다. 쓸 수 있는 이름: kids, family, teens, adults, seniors, pets, indoor, outdoor, watch, hands-on, food, market, walk, run, learn, heritage, nature, science, lights, fireworks, books, seasonal, halloween, christmas, year-end, new-year, evening, free, partly-paid, paid, book-ahead, walk-in."
    • changedOutput schema / properties / events / items / properties / tags / items / enum
      Previous value: -[
      -  "kids",
      -  "family",
      -  "teens",
      -  "adults",
      -  "seniors",
      -  "pets",
      -  "indoor",
      -  "outdoor",
      -  "watch",
      -  "hands-on",
      -  "food",
      -  "market",
      -  "walk",
      -  "learn",
      -  "heritage",
      -  "nature",
      -  "science",
      -  "lights",
      -  "fireworks",
      -  "books",
      -  "seasonal",
      -  "halloween",
      -  "christmas",
      -  "year-end",
      -  "new-year",
      -  "evening",
      -  "free",
      -  "partly-paid",
      -  "paid",
      -  "book-ahead",
      -  "walk-in"
      -]New value: +[
      +  "kids",
      +  "family",
      +  "teens",
      +  "adults",
      +  "seniors",
      +  "pets",
      +  "indoor",
      +  "outdoor",
      +  "watch",
      +  "hands-on",
      +  "food",
      +  "market",
      +  "walk",
      +  "run",
      +  "learn",
      +  "heritage",
      +  "nature",
      +  "science",
      +  "lights",
      +  "fireworks",
      +  "books",
      +  "seasonal",
      +  "halloween",
      +  "christmas",
      +  "year-end",
      +  "new-year",
      +  "evening",
      +  "free",
      +  "partly-paid",
      +  "paid",
      +  "book-ahead",
      +  "walk-in"
      +]
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnly/idempotent/non-destructive/closed-world), the description discloses two non-obvious behaviors: an implicit weekend time window when dates are omitted, and an automatic semantic re-search when the query yields nothing, with the substituted term reported in `related`. These are exactly the traits that change how an agent issues and interprets calls.

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?

Four short sentences with the scope and default behavior front-loaded; the first sentence carries the most decision-relevant information. Slight redundancy with the schema on pagination and the weekend default costs it a point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With eight all-optional parameters, a full output schema, and complete annotation coverage, the description covers the remaining burden: default time window, pagination continuation, and fallback search behavior. Nothing an agent needs to call it correctly is missing.

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 all eight parameters are already documented in the schema, including the weekend default for startDate/endDate and the nextOffset-to-offset pattern. The description restates those defaults rather than adding new semantics, which lands at the baseline 3.

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 opening states a specific verb and resource — finding public events (공개 행사) by date, region, and keyword — with a bracketed scope marker ("이번 주말: 축제·공연·전시"). It implicitly separates list-search from get_event, but never names a sibling outright, so a 4 rather than a 5.

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?

It gives clear operating context: omit dates to get this weekend's events, and use nextOffset as offset to continue. However, it never states when to prefer a sibling such as ask_events for free-form questions or get_event for a single event, so the routing guidance is incomplete.

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