Skip to main content
Glama

This Weekend (이번 주말)

행사 상세

get_event
Read-onlyIdempotent

[이번 주말: 축제·공연·전시 찾기] 행사 id로 일정, 장소, 요금, 예약 안내, 출처 링크를 가져옵니다. answers에는 언제, 몇 시, 얼마, 어디서, 주차, 누가 나오는지를 묻고 답한 줄이 있어서 가까운 역, 주차장, 출연진도 여기서 볼 수 있습니다.

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": {
      "id": "<id>"
    },
    "name": "get_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYessearch_events 결과에 있는 행사 id.

Output Schema

NameRequiredDescriptionDefault
idYes
feeYes제공처가 적은 요금 안내 문구. 없으면 null입니다.
urlYes사람이 보는 이 사이트의 행사 상세 페이지 주소.
cityYes
freeYestrue는 무료, false는 유료, null은 모름. fee에 금액이 적혀 있으면 true로 두지 않습니다.
tagsYes행사 글에서 읽은 태그: 누구와(kids, family 등), 어디서(indoor, outdoor), 무엇을, 주제, 저녁(evening), 요금(free, partly-paid, paid), 들어가기(book-ahead, walk-in). 없는 태그는 모름입니다.
hoursYes
placeYes
titleYes
addressYes
answersYes행사 페이지에 적힌 사실로 답한 질문(언제, 몇 시, 얼마, 어디, 주차, 출연). 답할 자료가 없는 질문은 빠집니다.
bookingYes
endDateYes
sourcesYes
summaryYes
audienceYes
categoryYes
districtYes
imageUrlYes
latitudeYes
amenitiesYes판정 모델이 행사 글을 읽고 확실할 때만 붙이는 편의: parking(available 주차 가능, limited 주차 어려움), pets(allowed 반려동물 동반 가능, banned 동반 불가), rain(goesOn 비가 와도 진행, mayStop 비가 오면 취소·연기될 수 있음), access(offered 휠체어·유모차 이용 가능). 없는 항목은 모름이고, 하나도 없으면 null입니다.
longitudeYes
organizerYes
sourceUrlYes자료를 가져온 곳의 안내 주소.
startDateYes
sourceNameYes
imageCreditYes
officialUrlYes주최 측 공식 안내 주소. 공공데이터 목록 페이지는 넣지 않습니다.
locationNoteYes좌표가 행사 장소 자체가 아닐 때(읍·면·동 일대, 여러 곳 중 대표 위치) 붙는 안내 문구입니다. 그 밖에는 null입니다.
wheelchairSeatsYes공연이 열리는 홀의 휠체어석 수입니다. 공연장이 KOPIS에 낸 장애인석 수를 그대로 옮겼고, 0이거나 비어 있으면 null입니다. null은 휠체어석이 없다는 뜻이 아니라 모른다는 뜻입니다.
scheduleNeedsReviewYestrue면 날짜가 확실하지 않으니 공식 안내에서 날짜를 다시 확인해야 합니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / wheelchairSeats
      Added value: +{
      +  "description": "공연이 열리는 홀의 휠체어석 수입니다. 공연장이 KOPIS에 낸 장애인석 수를 그대로 옮겼고, 0이거나 비어 있으면 null입니다. null은 휠체어석이 없다는 뜻이 아니라 모른다는 뜻입니다.",
      +  "minimum": 1,
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "id",
      -  "title",
      -  "startDate",
      -  "endDate",
      -  "hours",
      -  "scheduleNeedsReview",
      -  "place",
      -  "address",
      -  "city",
      -  "district",
      -  "category",
      -  "free",
      -  "fee",
      -  "tags",
      -  "url",
      -  "officialUrl",
      -  "sourceUrl",
      -  "sourceName",
      -  "summary",
      -  "audience",
      -  "organizer",
      -  "booking",
      -  "latitude",
      -  "longitude",
      -  "amenities",
      -  "locationNote",
      -  "imageUrl",
      -  "imageCredit",
      -  "sources",
      -  "answers"
      -]New value: +[
      +  "id",
      +  "title",
      +  "startDate",
      +  "endDate",
      +  "hours",
      +  "scheduleNeedsReview",
      +  "place",
      +  "address",
      +  "city",
      +  "district",
      +  "category",
      +  "free",
      +  "fee",
      +  "tags",
      +  "url",
      +  "officialUrl",
      +  "sourceUrl",
      +  "sourceName",
      +  "summary",
      +  "audience",
      +  "organizer",
      +  "booking",
      +  "latitude",
      +  "longitude",
      +  "amenities",
      +  "wheelchairSeats",
      +  "locationNote",
      +  "imageUrl",
      +  "imageCredit",
      +  "sources",
      +  "answers"
      +]
  2. Changed2 schema fields changed
    • addedOutput schema / properties / answers
      Added value: +{
      +  "description": "행사 페이지에 적힌 사실로 답한 질문(언제, 몇 시, 얼마, 어디, 주차, 출연). 답할 자료가 없는 질문은 빠집니다.",
      +  "items": {
      +    "properties": {
      +      "answer": {
      +        "type": "string"
      +      },
      +      "question": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "question",
      +      "answer"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "id",
      -  "title",
      -  "startDate",
      -  "endDate",
      -  "hours",
      -  "scheduleNeedsReview",
      -  "place",
      -  "address",
      -  "city",
      -  "district",
      -  "category",
      -  "free",
      -  "fee",
      -  "tags",
      -  "url",
      -  "officialUrl",
      -  "sourceUrl",
      -  "sourceName",
      -  "summary",
      -  "audience",
      -  "organizer",
      -  "booking",
      -  "latitude",
      -  "longitude",
      -  "amenities",
      -  "locationNote",
      -  "imageUrl",
      -  "imageCredit",
      -  "sources"
      -]New value: +[
      +  "id",
      +  "title",
      +  "startDate",
      +  "endDate",
      +  "hours",
      +  "scheduleNeedsReview",
      +  "place",
      +  "address",
      +  "city",
      +  "district",
      +  "category",
      +  "free",
      +  "fee",
      +  "tags",
      +  "url",
      +  "officialUrl",
      +  "sourceUrl",
      +  "sourceName",
      +  "summary",
      +  "audience",
      +  "organizer",
      +  "booking",
      +  "latitude",
      +  "longitude",
      +  "amenities",
      +  "locationNote",
      +  "imageUrl",
      +  "imageCredit",
      +  "sources",
      +  "answers"
      +]
  3. Changed1 schema field changed
    • changedOutput schema / 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"
      +]
  4. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish that this is a safe, read-only, idempotent operation. The description adds useful behavioral context about what information is available, including Q&A-style lines covering time, cost, location, parking, nearby stations, and cast, which helps an agent know what to expect beyond the safety hints.

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 two sentences and front-loads the core action of retrieving event details by id. The second sentence is somewhat long and awkwardly phrased, but it earns its place by describing the additional answer lines available.

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 an output schema present and full annotation coverage, the description is largely complete for a simple read-only detail lookup. It adequately describes the returned content, with only minor gaps such as not stating behavior for invalid or missing ids.

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%, and the single id parameter is fully documented as coming from search_events results. The description reinforces that the id is an event id but does not add additional syntax, validation, or lookup semantics beyond the schema.

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 clearly states a specific verb and resource: it retrieves event details by event id, including schedule, venue, fees, reservation guidance, and source links. It also clarifies the source of the id from search_events results, though it does not explicitly differentiate itself from siblings like get_event_coverage or ask_events.

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 implies usage after search_events by saying the id comes from search_events results, but it does not explicitly state when to use this tool versus ask_events, get_event_coverage, or other siblings. No exclusions or alternative-routing guidance are provided.

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