SetLuca

Official

by setluca

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Move a call to a new time

luca_reschedule_call

Destructive

Move a booked call to a new time, check slot availability, and return a fresh reschedule link. Moves provider calendars when possible; requires confirmation.

Instructions

Move a booked call to a new time and hand back a fresh reschedule link for the lead. Checks the new slot is open first, against the schedule of its booking type when it has one, and returns the open slots instead of moving the call when it is taken. A call with an idempotencyKey skips that check so a retry gets the original result back. A manual booking moves in Luca only. A Cal.com or Google Calendar booking moves on that calendar too. A Calendly, GoHighLevel or iClosed booking is refused so the coach can move it with the provider, and so is a provider booking with no calendar event, such as one from luca_book_call. Moving the call re-arms the lead's reminder for the new time, so pass confirm: true only after the coach approves the move. Example: call with { bookingId, slotAt: "2026-07-16T15:00:00Z", confirm: true } after the lead asked to push the call. No message about the move is sent: send the lead the link yourself, or draft the message through the review queue.

Input Schema

TableJSON Schema

Name	Required	Description
`slotAt`	Yes	ISO-8601 start time to move the call to, with an offset.
`confirm`	No	This 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.
`provider`	No	The coach's booking provider. Used only for the availability check, and only when the booking has no booking type. The booking keeps the provider it already has. Pass it when the coach is not on Calendly, or the availability check reads the wrong calendar.
`bookingId`	Yes	The booking to move.
`workspaceId`	No	Optional Luca workspace id override.
`workspaceSlug`	No	Optional Luca workspace slug override.
`expiresInHours`	No	How long the new reschedule link stays usable. Defaults to 168 hours.
`idempotencyKey`	No	Reuse the same key when retrying this exact reschedule. A keyed call skips the availability check and lets the API replay the first result.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes
`provenance`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Oct 21, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only say destructive/openWorld/non-idempotent; the description adds what actually happens: availability is validated (against the booking type's schedule), open slots are returned instead of a move when taken, side effects propagate to Cal.com/Google Calendar, the lead's reminder is re-armed, and no message is sent to the lead. That is substantial context beyond the annotations and does not contradict them.

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, then conditions, then the side-effect and messaging caveat, with a concrete example. It is long (eight-plus sentences) and repeats some schema-documented details about confirm and idempotencyKey, but almost every sentence adds decision-relevant information.

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?

Covers refusal cases, provider-specific behavior, idempotent retry semantics, reminder re-arming, and the out-of-band messaging requirement, and an output schema exists so return shape needn't be spelled out. An agent has everything needed to invoke this safely.

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 semantics: confirm is a gating approval after coach sign-off, provider only affects the availability check and never changes the booking's provider, and idempotencyKey bypasses the slot check for retries. expiresInHours is only implicitly covered via 'fresh reschedule link'.

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 ('Move a booked call to a new time') plus the second product of the call ('hand back a fresh reschedule link for the lead'). This is clearly distinct from siblings like luca_bookings_update and luca_bookings_cancel, which mutate different aspects of a booking.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly gives the when/when-not: a call with idempotencyKey skips the check; Calendly/GoHighLevel/iClosed bookings are refused; provider bookings without a calendar event are refused; confirm: true only after coach approval. It also names a follow-up path (draft the message through the review queue) rather than leaving the agent to infer it.

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

Deploy Server