Skip to main content
Glama
Sign In
SetLuca

SetLuca

Official
by setluca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Backfill a booking's call event

luca_call_events_backfill
Idempotent

Create a call event for a booking that predates automatic creation, then queue its summary. Safe to call twice: an existing call event comes back as is.

Instructions

Create a call event for a booking that predates automatic creation, then queue its summary. Safe to call twice: an existing call event comes back as is.

Luca operation: POST /api/call-events/backfill/{bookingId} Required scopes: call_events:write Required OAuth scope: luca:draft; data sensitivity: full_content Requires Idempotency-Key. Provide idempotencyKey for safe retries, or the server will generate one. 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": {
      "bookingId": "<bookingId>"
    },
    "name": "luca_call_events_backfill"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookingIdYes
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.2/5.0
Behavior4/5

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

The description adds meaningful behavioral context beyond annotations: it queues a summary as a side effect and returns an existing call event unchanged on repeat calls. These points are consistent with idempotentHint=true and destructiveHint=false, though the idempotency statement itself overlaps with the annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and idempotency guarantee are front-loaded, followed by operation, scopes, sensitivity, idempotency-key behavior, and workspace override. The information is dense but every section is relevant to correct invocation.

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?

The description covers the primary mutation, its side effect, idempotency, required scopes, sensitivity, and workspace override; an output schema exists so return values need not be explained. Minor gaps remain around what happens if the booking is ineligible or nonexistent.

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 coverage is 75%, and the description mostly restates what the schema already documents for idempotencyKey and workspace overrides. It does not add deeper semantics for bookingId or explain error cases, so the schema remains the primary source of parameter meaning.

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 states a specific verb and resource ('Create a call event for a booking') plus a precise eligibility condition ('predates automatic creation'), which distinguishes it from sibling tools such as luca_call_events_get or luca_call_events_by_booking.

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 clearly states when the tool applies: only for bookings that predate automatic call-event creation. It also says the tool is safe to call twice, but it does not name alternative tools or explicitly describe when *not* to use this backfill path.

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