Sessionize
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SESSIONIZE_EVENT_ID | No | Default Sessionize event ID (can be overridden per tool call) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| findSessionC | Search sessions by title or description. Returns matching sessions with full details. |
| findSpeakerC | Search for a speaker by name in a Sessionize event. Returns matching speakers with full details including bio and social links. |
| getScheduleB | Get the event schedule/agenda from Sessionize. Returns the schedule organized by day and time slot. Note: Schedule may be empty if the event hasn't configured session times. |
| getSessionsB | List all sessions for a Sessionize event. Returns session titles, descriptions, speakers, and schedule information. |
| getSessionsBySpeakerB | Get all sessions for a specific speaker. Returns the list of sessions the speaker is presenting. |
| getSpeakersA | List all speakers for a Sessionize event. Returns speaker names, bios, taglines, and social links. If eventId is not provided, uses the configured default event. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Most tools have distinct purposes, but 'getSessions' and 'findSession' could cause some confusion as both retrieve session information. 'getSessions' lists all sessions, while 'findSession' searches by criteria, but the overlap might lead to misselection in certain contexts.
All tool names follow a consistent camelCase pattern with clear verb-noun combinations (e.g., findSession, getSchedule, getSessionsBySpeaker). The naming is predictable and readable throughout the set.
With 6 tools, this is well-scoped for a Sessionize server, covering core operations like searching, listing, and retrieving sessions and speakers. Each tool has a clear purpose and contributes to the functionality without being excessive or sparse.
The tool set provides good coverage for reading and searching sessions and speakers, including schedule retrieval. However, there are minor gaps such as lack of update or delete operations for events, which might be expected in a full CRUD lifecycle, but agents can likely work around this for typical query-focused use cases.