Skip to main content
Glama

RooQuiz

by com.rooquiz.payload
OverviewDiscussionsAdmin

List bookings

list_bookings
Read-only

List the 1:1 bookings (discovery calls / consultations booked from a quiz report page) of the current team, earliest first. Each item carries the time range, status, meeting type, the attendee, the source quiz and submission, and the lead owner who should handle it. Filter by status / quiz / respondent / time range. Typical use: status "pending" lists the approval queue waiting on someone. Reference a booking by its bookingId; the attendee name / email come back masked.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoOnly bookings starting strictly before this ISO datetime, optional
fromNoOnly bookings starting on/after this ISO datetime, optional
pageNoPage number (1-based), default 1
sortNoSort by start time, default startAt (earliest first)
limitNoItems per page, default 20, max 100
formIdNoOnly bookings that came from this quiz, optional
statusNoFilter by status. pending = a request awaiting approval (the team has requireApproval on), scheduled = a confirmed meeting, the rest are terminal. Optional.
recordIdNoOnly bookings tied to this submission record, optional
examineeIdNoOnly bookings by this respondent — the internal examinee id (get_lead's respondent.id), not the examineeId business code. Optional.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page returned
itemsNoThe page of bookings (earliest first by default)
totalDocsNoTotal bookings matching the filter
totalPagesNoTotal pages available

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedOutput schema / properties / items / items / properties / form / description
      Previous value: -"The quiz the booking came from"New value: +"The quiz the booking came from as { id, title }"
    • changedOutput schema / properties / items / items / properties / form / type
      Previous value: -[
-  "string",
-  "number",
-  "null"
-]New value: +[
+  "object",
+  "null"
+]
    • changedOutput schema / properties / items / items / properties / record / description
      Previous value: -"The submission the booking is tied to"New value: +"The submission the booking is tied to as { id, serialNumber, shareToken }"
    • changedOutput schema / properties / items / items / properties / record / type
      Previous value: -[
-  "string",
-  "number",
-  "null"
-]New value: +[
+  "object",
+  "null"
+]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral detail beyond that: the API returns earliest first, descriptions fields per item, masks attendee contact info, and indicates the 'pending' status represents an unapproved booking. This adds meaningful context without redundancy or contradiction.

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 compact and front-loads the primary action and scope. All sentences contribute meaningful context: sorting, returned fields, filters, typical use, and attention-masking. It could drop the slightly redundant 'list' wording, but overall it earns its place without significant bloat.

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 a full input schema, an output schema, and clear annotations, the description adds what the agent still needs: the meaning of the 'pending' status, the masked/contact-handling behavior, and how to reference a booking by bookingId. Combined with the structured data, the description is sufficient for an agent to select and invoke the tool correctly.

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%, so the baseline is 3. The description adds a few semantic hints not always in the schema, such as the meaning of 'pending' as being the approval queue and the ability to filter by status/quiz/respondent/time range. But it doesn't need to compensate for schema gaps, and beyond those hints it functions mostly as a summary.

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 identifies the tool as listing 1:1 bookings for the current team, specifies the sort order (earliest first), and enumerates what each item contains. It also mentions it filters by status, quiz, respondent, and time range, which distinguishes it from generic list tools and the related booking mutation tools.

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 gives a concrete typical use case: using status "pending" to view the approval queue waiting on someone. It surfaces privacy behavior (attendee name/email masked) and how to reference a booking by bookingId. It doesn't explicitly state when not to use this tool versus sibling booking tools like review_booking or update_booking_status, but the intended read-only list usage is clear enough.

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

All RooQuiz toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources