Skip to main content
Glama
Sign In
SetLuca

SetLuca

Official
by setluca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Resolve a booking's lifecycle flag

luca_bookings_lifecycle_resolution
Destructive

Resolve a booking whose record disagrees with the provider by dismissing a duplicate or setting its status to confirmed, cancelled, completed, or no_show.

Instructions

Settle one booking whose record disagrees with the provider's: dismiss the duplicate, or set it confirmed, cancelled, completed, or no_show. To retry the sync, use luca_bookings_provider_sync_retry.

Luca operation: POST /api/bookings/{id}/lifecycle-resolution 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_lifecycle_resolution"
  }
}

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. First observedv0.4.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses required scopes, OAuth scope, data sensitivity, idempotency-key behavior, workspace override support, and the critical requirement to pass confirm: true for a destructive real-world side effect. This substantially enriches the behavioral picture already provided by destructiveHint and openWorldHint.

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 front-loaded with the core action and alternative, then moves through operational constraints in a structured way. It is somewhat list-heavy and repeats the destructive nature already in annotations, but each section adds practical information for invoking the tool correctly.

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?

For a destructive booking mutation with an output schema and annotations, the description covers the purpose, when to use it, the relevant alternative, scopes, idempotency, confirmation, and workspace overrides. Nothing critical for correct invocation appears to be 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?

The description explains the body choices in prose (dismiss duplicate or set a lifecycle status), clarifies the purpose of idempotencyKey for safe retries with server-generated fallback, and explains confirm and workspace override parameters. The schema already describes several parameters, but the description adds useful operational meaning, especially around confirmation and retry safety.

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 names a specific operation ('Settle one booking whose record disagrees with the provider's') and enumerates the possible lifecycle outcomes: dismiss duplicate, confirmed, cancelled, completed, or no_show. It also explicitly distinguishes this from the sync-retry sibling, so an agent can identify it without opening the schema.

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?

It gives a clear usage condition ('one booking whose record disagrees with the provider's') and points to luca_bookings_provider_sync_retry for the alternative case of retrying sync. It does not explicitly state when not to use the tool, but the condition and named alternative make the intended context clear.

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