Skip to main content
Glama
Sign In
SetLuca

SetLuca

Official
by setluca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List bookings

luca_bookings_list
Read-onlyIdempotent

Lists bookings with filters for status, upcoming date, lead, and pagination so you can review scheduled calls and manage workspace-specific booking records.

Instructions

List bookings. Query supports limit, cursor, status, and upcoming.

Luca operation: GET /api/bookings Required scopes: bookings:read Required OAuth scope: luca:read; data sensitivity: full_content Does not require idempotency. Use workspaceId or workspaceSlug to override the default workspace configured by environment.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "luca_bookings_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
maxPagesNoMax pages the server auto-fetches and merges (default 10, hard cap 50). If more remain, the result is marked truncated with a nextCursor to continue.
workspaceIdNoOptional Luca workspace id override.
workspaceSlugNoOptional Luca workspace slug override.

Output Schema

NameRequiredDescriptionDefault
resultYes
provenanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.2
    • changedOutput schema / properties / result / x-luca-redacted-fields
      Previous value: -[
-  "bookings[].rawPayload"
-]New value: +[
+  "bookings[].guestCancelNote",
+  "bookings[].leadName",
+  "bookings[].rawPayload"
+]
  2. First observedv0.4.0

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, closed-world), it discloses the backing operation GET /api/bookings, required scopes (bookings:read, luca:read), full_content data sensitivity, and default-workspace override behavior. These are genuinely useful facts an agent cannot get from the annotations alone; only pagination/truncation behavior is left to the schema.

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?

Short, front-loaded, and organized into discrete fact lines (operation, scopes, idempotency, workspace override) rather than prose. The opening 'List bookings' partially duplicates the title but otherwise there is little waste.

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?

An output schema covers return values, annotations cover the safety profile, and the schema documents maxPages/cursor pagination and workspace overrides. The description closes the remaining gaps — auth scopes, sensitivity, endpoint, and scope-required workspace selection — so an agent has what it needs to call this 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 75%, and the description enumerates limit, cursor, status, and upcoming — but omits leadId, which exists in the schema, and adds no format or semantics for status/upcoming (no enum values). Its parameter content largely restates the schema, so baseline 3 is appropriate.

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?

States a specific verb and resource ('List bookings') and names the query facets it supports, which clearly separates it from mutation siblings like luca_bookings_create or luca_bookings_cancel. It does not explicitly distinguish itself from read-oriented siblings such as luca_bookings_availability or luca_bookings_brief, so it falls short of full sibling differentiation.

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 context (listing with limit/cursor/status/upcoming filters, workspace override) but never says when to choose this tool over luca_bookings_brief, luca_bookings_availability, or other list siblings. Usage is implied by the resource name rather than stated as selection guidance.

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

Deploy Server

Other Tools