pifini

Get event details

get_event

Read-onlyIdempotent

Full details for one event by slug: description, venue, date/time, and available ticket types with prices and remaining stock. Use the slug from search_events.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	Event slug from search_events

Output Schema

TableJSON Schema

Name	Required	Description
`url`	No
`city`	No
`slug`	No
`price`	No
`title`	No
`country`	No
`ends_at`	No
`summary`	No
`website`	No
`category`	No
`currency`	No
`timezone`	No	IANA timezone of the venue, e.g. America/Mexico_City. Null when unknown.
`starts_at`	No	Exact start instant, ISO-8601 UTC. Do NOT format this for a human — it is the wrong calendar day in most of the region. Use local_date / local_time.
`local_date`	No	The date the event actually happens where it happens, YYYY-MM-DD. Quote this one.
`local_time`	No	Local start time, HH:MM 24h. Null when start_time_known is false — say nothing about the time in that case.
`description`	No
`entry_model`	No
`ticket_types`	No
`location_name`	No
`organizer_url`	No
`attendee_count`	No
`organizer_name`	No
`cover_image_url`	No
`start_time_known`	No	False when only the date is known and the stored hour is a placeholder. Never present a start time when this is false.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed5 schema fields changedAug 14, 2026

addedOutput schema / properties / local_date

Added value: +{
+  "description": "The date the event actually happens where it happens, YYYY-MM-DD. Quote this one.",
+  "type": "string"
+}

addedOutput schema / properties / local_time

Added value: +{
+  "description": "Local start time, HH:MM 24h. Null when start_time_known is false — say nothing about the time in that case.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / start_time_known

Added value: +{
+  "description": "False when only the date is known and the stored hour is a placeholder. Never present a start time when this is false.",
+  "type": "boolean"
+}

addedOutput schema / properties / starts_at / description

Added value: +"Exact start instant, ISO-8601 UTC. Do NOT format this for a human — it is the wrong calendar day in most of the region. Use local_date / local_time."

addedOutput schema / properties / timezone

Added value: +{
+  "description": "IANA timezone of the venue, e.g. America/Mexico_City. Null when unknown.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed1 schema field changedAug 5, 2026

addedOutput schema / properties / ticket_types / items

Added value: +{
+  "properties": {
+    "currency": {
+      "type": "string"
+    },
+    "description": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "name": {
+      "type": "string"
+    },
+    "price": {
+      "type": "number"
+    },
+    "remaining": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "sales_end_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "ticket_type_id": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "ticket_type_id",
+    "name",
+    "price",
+    "currency"
+  ],
+  "type": "object"
+}

Changed1 schema field changedJul 28, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "attendee_count": {
+      "type": "number"
+    },
+    "category": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "city": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "country": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "cover_image_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "currency": {
+      "type": "string"
+    },
+    "description": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "ends_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "entry_model": {
+      "type": "string"
+    },
+    "location_name": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "organizer_name": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "organizer_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "price": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "slug": {
+      "type": "string"
+    },
+    "starts_at": {
+      "type": "string"
+    },
+    "summary": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "ticket_types": {
+      "type": "array"
+    },
+    "title": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    },
+    "website": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedJul 2, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds value by explicitly enumerating the returned fields (venue, date/time, ticket types with prices and remaining stock), giving the agent a preview of the response content beyond what annotations convey.

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?

The description is two concise sentences, front-loaded with the core purpose and then a practical usage hint. No redundant words or repetition of structured fields, making every sentence earn its place.

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 one simple parameter, high schema coverage, an output schema, and complete annotations, the description adequately covers the tool's behavior and usage. It mentions the key response elements, making it self-sufficient for a straightforward getter.

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% with a description 'Event slug from search_events'. The tool description repeats this with 'Use the slug from search_events', reinforcing but not adding new meaning beyond the schema. The baseline is 3 given high schema coverage.

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 clearly states it provides 'Full details for one event by slug' and lists specific response components (description, venue, date/time, ticket types with prices and stock). This distinguishes it from siblings like search_events, which find events, and get_place, which retrieves place details.

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?

The description tells the user to 'Use the slug from search_events', providing a clear prerequisite and source for the input. It implies this tool is for fetching a specific event's full details, but does not explicitly state when not to use it or offer alternative tool comparisons beyond the slug hint.

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

All pifini tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool has a distinct purpose: search vs. get by slug for both events and places, plus a category lookup and a checkout action. The clear separation between search and detail retrieval prevents confusion. No two tools appear to overlap in functionality.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case: create_, get_, list_, search_. The naming is uniform and predictable, making it easy to infer what each tool does from its name.

Tool Count5/5

With 6 tools, the server is well-scoped for its purpose of exploring events and places. Each tool covers a distinct aspect—search, detail retrieval, category lookup, and ticket checkout—without redundancy or bloat. This is within the ideal range for a focused MCP server.

Completeness4/5

The tool set covers the main workflows: discovering events and places, viewing details, and purchasing tickets. A minor gap is the lack of a category taxonomy for events, as list_categories is specific to places, but event categories are returned in search results and can be used ad hoc. Overall, the surface is functionally complete for consumers.

Resources

Need Help?