Skip to main content
Glama
Sign In
SetLuca

SetLuca

Official
by setluca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Reschedule or edit a booking

luca_bookings_update
Destructive

Reschedule or update booking status. A Google Calendar or Cal.com booking changes on that calendar too, and the calendar can email the lead about it.

Instructions

Reschedule or update booking status. A Google Calendar or Cal.com booking changes on that calendar too, and the calendar can email the lead about it.

Luca operation: PATCH /api/bookings/{id} Required scopes: bookings:write Required OAuth scope: luca:queue_ops; data sensitivity: full_content Requires Idempotency-Key. Provide idempotencyKey for safe retries, or the server will generate one. Destructive: has a real-world side effect. You must pass confirm: true; the call is rejected without it. Use workspaceId or workspaceSlug to override the default workspace configured by environment.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>",
      "body": "<body>"
    },
    "name": "luca_bookings_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
bodyYes
confirmNoThis tool has a real-world side effect: it messages real leads, books, moves, or cancels a call, changes a lead's consent, imports leads, writes to a connected calendar or CRM, sends workspace events to an outside URL, or re-triggers downstream automations. Pass confirm: true to proceed; the call is rejected without it.
workspaceIdNoOptional Luca workspace id override.
workspaceSlugNoOptional Luca workspace slug override.
idempotencyKeyNoStable key for safe retries. If omitted, the MCP server generates a unique key for this call.

Output Schema

NameRequiredDescriptionDefault
resultYes
provenanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.1
    • addedInput schema / properties / body / properties / rawPayload / additionalProperties
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "object"
+    },
+    {
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
  2. First observedv0.4.0

TDQS

A4.3/5.0
Behavior5/5

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

Goes well past the annotations by disclosing the real-world consequence chain: the change propagates to a connected Google Calendar or Cal.com calendar and the calendar may email the lead. It also explains the idempotency-key behavior (server generates one if omitted) and the confirm-gate rejection, all of which are behavioral details annotations alone do not convey.

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?

Front-loaded with the action and the consequence, then broken into scannable labeled lines for scopes, idempotency, confirm, and workspace override. There is mild redundancy, since the confirm requirement is restated from the schema's own description, but every line carries actionable information.

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?

For a destructive mutation with an output schema, the description covers side effects, auth/scopes, idempotency, and the confirm gate, which is most of what an agent needs. The remaining gap is mutation semantics on the body: with additionalProperties false, it is unstated whether partial edits clear unset fields, and the status/provider enum usage is unaddressed.

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?

Parameter handling is handled largely by the schema, which documents confirm, workspaceId, workspaceSlug, and idempotencyKey at 67% coverage. The description mentions confirm and idempotencyKey but adds no meaning to the body fields (status enum values, provider, slotAt/endAt, rawPayload, provider*Id), so it neither compensates for the remaining coverage gap nor adds value on top of the schema.

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?

States a specific verb and resource (reschedule / update booking status) and names the concrete endpoint (PATCH /api/bookings/{id}), which distinguishes it from the sibling create/cancel tools in the bookings family. An agent can tell from the first sentence alone what this tool mutates.

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?

Gives strong operational context: required scopes (bookings:write, luca:queue_ops), the mandatory Idempotency-Key, the confirm: true gate, and workspaceId/workspaceSlug overrides. It stops short of naming an alternative (e.g., luca_bookings_cancel) or saying when a status change should go through this tool rather than the cancel path, so it is clear context without explicit exclusions.

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