Get Event Feedback Prompt
get_event_feedback_promptRead-only
Use this when a user needs a short post-event feedback prompt.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| event_id | Yes | ||
| attended_at | No |
events
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Changed2 schema fields changed
- removed
Input schema / properties / attended_at / descriptionRemoved value: -"Optional ISO date/time or YYYY-MM-DD the user attended or planned to attend." - changed
Output schema / (root)Previous value: -{ - "anyOf": [ - { - "properties": { - "assistant_instruction": { - "type": "string" - }, - "attended_at": { - "type": [ - "string", - "null" - ] - }, - "event": { - "properties": { - "attendance_count": { - "type": [ - "number", - "null" - ] - }, - "calendar_url": { - "description": "Prefilled Google Calendar link. Offer as 'Add to calendar'.", - "type": [ - "string", - "null" - ] - }, - "city": { - "type": [ - "string", - "null" - ] - }, - "description": { - "description": "Short one-line event description for display.", - "type": [ - "string", - "null" - ] - }, - "directions_url": { - "description": "Google Maps directions link. Offer as 'Get directions'.", - "type": [ - "string", - "null" - ] - }, - "ends_at": { - "type": [ - "string", - "null" - ] - }, - "event_types": { - "items": { - "type": "string" - }, - "type": "array" - }, - "event_url": { - "type": "string" - }, - "genres": { - "items": { - "type": "string" - }, - "type": "array" - }, - "id": { - "type": "string" - }, - "lineup": { - "items": { - "type": "string" - }, - "type": "array" - }, - "price": { - "type": [ - "string", - "null" - ] - }, - "source": { - "type": [ - "string", - "null" - ] - }, - "starts_at": { - "type": [ - "string", - "null" - ] - }, - "ticket_url": { - "type": [ - "string", - "null" - ] - }, - "title": { - "type": "string" - }, - "venue": { - "type": [ - "string", - "null" - ] - }, - "vibe": { - "items": { - "type": "string" - }, - "type": "array" - } - }, - "required": [ - "id", - "title", - "event_url" - ], - "type": "object" - }, - "questions": { - "items": { - "type": "string" - }, - "type": "array" - } - }, - "required": [ - "event", - "attended_at", - "questions", - "assistant_instruction" - ], - "type": "object" - }, - { - "properties": { - "assistant_instruction": { - "type": "string" - }, - "cause": { - "type": [ - "string", - "null" - ] - }, - "classification": { - "type": [ - "string", - "null" - ] - }, - "code": { - "type": [ - "string", - "null" - ] - }, - "error": { - "type": "string" - }, - "hostname": { - "type": [ - "string", - "null" - ] - }, - "retryable": { - "type": "boolean" - }, - "status": { - "type": [ - "number", - "null" - ] - }, - "type": { - "type": "string" - }, - "url": { - "type": [ - "string", - "null" - ] - } - }, - "required": [ - "error" - ], - "type": "object" - } - ], - "type": "object" -}New value: +null
Changed2 schema fields changed
- added
Input schema / properties / attended_at / descriptionAdded value: +"Optional ISO date/time or YYYY-MM-DD the user attended or planned to attend." - changed
Output schema / (root)Previous value: -nullNew value: +{ + "anyOf": [ + { + "properties": { + "assistant_instruction": { + "type": "string" + }, + "attended_at": { + "type": [ + "string", + "null" + ] + }, + "event": { + "properties": { + "attendance_count": { + "type": [ + "number", + "null" + ] + }, + "calendar_url": { + "description": "Prefilled Google Calendar link. Offer as 'Add to calendar'.", + "type": [ + "string", + "null" + ] + }, + "city": { + "type": [ + "string", + "null" + ] + }, + "description": { + "description": "Short one-line event description for display.", + "type": [ + "string", + "null" + ] + }, + "directions_url": { + "description": "Google Maps directions link. Offer as 'Get directions'.", + "type": [ + "string", + "null" + ] + }, + "ends_at": { + "type": [ + "string", + "null" + ] + }, + "event_types": { + "items": { + "type": "string" + }, + "type": "array" + }, + "event_url": { + "type": "string" + }, + "genres": { + "items": { + "type": "string" + }, + "type": "array" + }, + "id": { + "type": "string" + }, + "lineup": { + "items": { + "type": "string" + }, + "type": "array" + }, + "price": { + "type": [ + "string", + "null" + ] + }, + "source": { + "type": [ + "string", + "null" + ] + }, + "starts_at": { + "type": [ + "string", + "null" + ] + }, + "ticket_url": { + "type": [ + "string", + "null" + ] + }, + "title": { + "type": "string" + }, + "venue": { + "type": [ + "string", + "null" + ] + }, + "vibe": { + "items": { + "type": "string" + }, + "type": "array" + } + }, + "required": [ + "id", + "title", + "event_url" + ], + "type": "object" + }, + "questions": { + "items": { + "type": "string" + }, + "type": "array" + } + }, + "required": [ + "event", + "attended_at", + "questions", + "assistant_instruction" + ], + "type": "object" + }, + { + "properties": { + "assistant_instruction": { + "type": "string" + }, + "cause": { + "type": [ + "string", + "null" + ] + }, + "classification": { + "type": [ + "string", + "null" + ] + }, + "code": { + "type": [ + "string", + "null" + ] + }, + "error": { + "type": "string" + }, + "hostname": { + "type": [ + "string", + "null" + ] + }, + "retryable": { + "type": "boolean" + }, + "status": { + "type": [ + "number", + "null" + ] + }, + "type": { + "type": "string" + }, + "url": { + "type": [ + "string", + "null" + ] + } + }, + "required": [ + "error" + ], + "type": "object" + } + ], + "type": "object" +}
Changed2 schema fields changed
- removed
Input schema / properties / attended_at / descriptionRemoved value: -"Optional ISO date/time or YYYY-MM-DD the user attended or planned to attend." - changed
Output schema / (root)Previous value: -{ - "anyOf": [ - { - "properties": { - "assistant_instruction": { - "type": "string" - }, - "attended_at": { - "type": [ - "string", - "null" - ] - }, - "event": { - "properties": { - "attendance_count": { - "type": [ - "number", - "null" - ] - }, - "calendar_url": { - "description": "Prefilled Google Calendar link. Offer as 'Add to calendar'.", - "type": [ - "string", - "null" - ] - }, - "city": { - "type": [ - "string", - "null" - ] - }, - "description": { - "description": "Short one-line event description for display.", - "type": [ - "string", - "null" - ] - }, - "directions_url": { - "description": "Google Maps directions link. Offer as 'Get directions'.", - "type": [ - "string", - "null" - ] - }, - "ends_at": { - "type": [ - "string", - "null" - ] - }, - "event_types": { - "items": { - "type": "string" - }, - "type": "array" - }, - "event_url": { - "type": "string" - }, - "genres": { - "items": { - "type": "string" - }, - "type": "array" - }, - "id": { - "type": "string" - }, - "lineup": { - "items": { - "type": "string" - }, - "type": "array" - }, - "price": { - "type": [ - "string", - "null" - ] - }, - "source": { - "type": [ - "string", - "null" - ] - }, - "starts_at": { - "type": [ - "string", - "null" - ] - }, - "ticket_url": { - "type": [ - "string", - "null" - ] - }, - "title": { - "type": "string" - }, - "venue": { - "type": [ - "string", - "null" - ] - }, - "vibe": { - "items": { - "type": "string" - }, - "type": "array" - } - }, - "required": [ - "id", - "title", - "event_url" - ], - "type": "object" - }, - "questions": { - "items": { - "type": "string" - }, - "type": "array" - } - }, - "required": [ - "event", - "attended_at", - "questions", - "assistant_instruction" - ], - "type": "object" - }, - { - "properties": { - "assistant_instruction": { - "type": "string" - }, - "cause": { - "type": [ - "string", - "null" - ] - }, - "classification": { - "type": [ - "string", - "null" - ] - }, - "code": { - "type": [ - "string", - "null" - ] - }, - "error": { - "type": "string" - }, - "hostname": { - "type": [ - "string", - "null" - ] - }, - "retryable": { - "type": "boolean" - }, - "status": { - "type": [ - "number", - "null" - ] - }, - "type": { - "type": "string" - }, - "url": { - "type": [ - "string", - "null" - ] - } - }, - "required": [ - "error" - ], - "type": "object" - } - ], - "type": "object" -}New value: +null
- First observed
TDQS
A3.5/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so the read-only safety profile is covered. The description adds the output character ('short post-event feedback prompt') but does not explain what the tool does with attended_at, whether it returns a template or generates dynamic text, or what the payload contains.
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?
A single, front-loaded sentence with no filler or repetition. It communicates both the use-case and the result type efficiently.
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?
For a simple read-only prompt tool this is close to sufficient, but because there is no output schema, the description should explicitly state what is returned. The optional attended_at parameter also needs at least a brief explanation to make invocation fully unambiguous.
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 description coverage is 0%, and the description gives no guidance on event_id or attended_at. The parameter names are somewhat self-explanatory, especially event_id, but attended_at's role is entirely unexplained, leaving an agent to guess whether it affects prompt wording or is optional context.
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 identifies the resource ('a short post-event feedback prompt') and the situation ('when a user needs'), which sets it apart from siblings like record_event_feedback. It stops short of an explicit tool verb such as 'returns' or 'generates', so the action is slightly implied rather than stated.
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 provides a clear trigger condition: use this when a user needs a short post-event feedback prompt. It does not explicitly exclude alternatives or name when not to use it, but the sibling set makes the distinction fairly obvious, especially compared to record_event_feedback.
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.
TDQS
B3.2/5.0
Disambiguation4/5
Most tools map to distinct actions across search, recommendations, preferences, tickets, and feedback, with clear descriptions. The only real ambiguity is between recommend_events and recommend_events_for_user, plus some follow-up overlap, but boundaries are mostly clear.
Naming Consistency4/5
Tool names follow a consistent imperative verb_noun pattern and use snake_case throughout. Minor inconsistency exists in event vs events pluralization and interchangeable create/save verbs, but the overall pattern is predictable.
Tool Count3/5
23 tools is a large surface for an events assistant, landing in the 16-25 range that feels heavy. The count is defensible given the breadth of features, but it is borderline and somewhat difficult to navigate.
Completeness4/5
The set covers the core consumer journey well: search, recommendations, preference onboarding and CRUD, ticket quoting and purchase, and post-event feedback. Missing order-status or refund/cancellation endpoints are minor gaps, but primary workflows do not hit dead ends.