Skip to main content
Glama
dragosh29

Bookwhen MCP server

by dragosh29

List events

list_events
Read-onlyIdempotent

Retrieve Bookwhen classes, courses, and workshops with dates, attendee limits, tags, and locations. Filter by title, tag, calendar, or date range to find scheduled events.

Instructions

List events (classes, courses, workshops) with date, attendee limit and count, tags and location ID. The API returns events from today onwards unless from is given; every filter is combined with AND, and multiple values within one filter are sent comma-separated. Pages are followed until the API reports no next page or max_results is reached.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoNon-inclusive end, YYYYMMDD or YYYYMMDDHHMMSS (filter[to])
fromNoInclusive start, YYYYMMDD or YYYYMMDDHHMMSS (filter[from]; the API defaults to today)
tagsNoTag words to include (filter[tag])
titleNoEntry titles to search for (filter[title])
detailNoEntry details text to search for (filter[detail])
compactNoCombine the events of a course into a single virtual event (filter[compact])
calendarNoCalendars (schedule pages) to restrict to (filter[calendar])
locationNoLocation slugs to include (filter[location])
max_resultsNoMaximum number of events to return
include_locationNoSide-load each event's location (include=location). Slower; the API recommends includes for single-event requests
include_contact_detailsNoStop redacting email addresses and phone numbers from titles, details and location text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds substantial extra behavior: the default date window when `from` is omitted, AND-combination of filters, comma-separated multi-values within one filter, and automatic pagination until no next page or max_results. These are traits an agent could not infer from the structured fields.

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?

Three tight sentences: purpose and scope first, then defaults and filter-combination rules, then pagination. No filler, and the most decision-relevant information (default date window) is front-loaded.

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 11 optional parameters, no output schema, and a fully documented schema, the description is nearly sufficient: it explains filtering semantics, defaults, and pagination. It could say more about ordering or what pagination metadata accompanies the events, but nothing an agent needs in order to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine cross-parameter semantics the schema does not convey: every filter is AND-ed together and multiple values inside a single filter are sent comma-separated. That is real meaning beyond per-parameter docs, though individual parameter formats are left to 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?

Names a specific verb and resource and disambiguates the resource with synonyms ('classes, courses, workshops'), plus lists the returned fields (date, attendee limit and count, tags, location ID). It does not explicitly distinguish itself from siblings like list_class_passes or get_event, so it stops short of the top band.

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 gives operating context (default range is today onwards, filters combined with AND) but never states when to choose this tool over get_event or the other list_* siblings, nor any when-not conditions. Usage is implied rather than prescribed.

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