Skip to main content
Glama
Sign In
SetLuca

SetLuca

Official
by setluca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Pause a lead's cadence

luca_cadences_pause
DestructiveIdempotent

Pause (cancel) a lead's running rescue cadence with an optional reason.

Instructions

Pause (cancel) a lead's running rescue cadence with an optional reason.

Luca operation: POST /api/leads/{id}/cadence/pause Required scopes: cadences:write Required OAuth scope: luca:queue_ops; data sensitivity: redacted 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": {
      "id": "<id>"
    },
    "name": "luca_cadences_pause"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
bodyNo
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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.1
    • changedInput schema / required
      Previous value: -[
-  "id",
-  "body"
-]New value: +[
+  "id"
+]
  2. First observedv0.4.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, yet the description adds genuinely new context: required scopes (cadences:write, luca:queue_ops), data sensitivity marking, and the fact that the server generates an idempotency key when omitted. The notable omission is reversibility — it never says whether a paused cadence can be resumed or what happens to in-flight work, which matters given the destructive hint.

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?

Purpose is front-loaded in the first line, followed by compact operational metadata. The raw endpoint line ("POST /api/leads/{id}/cadence/pause") is largely redundant but short, and no sentence is wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values needn't be explained, and annotations already cover the safety/idempotency profile. Still missing for a destructive mutation: whether the pause is reversible, how to resume, and how it differs from the similarly named sibling — all things an agent needs before invoking.

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 60%: workspaceId, workspaceSlug, and idempotencyKey are already documented in the schema and the description mostly restates them. It does add that the reason is optional and that `id` refers to a lead, but neither is elaborated, so it only marginally beats the schema.

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: "Pause (cancel) a lead's running rescue cadence," which is far more precise than the title alone. However, it offers no differentiation from the near-identical sibling luca_pause_cadence (nor from luca_cadences_rescue_start, its natural inverse), so an agent cannot tell which pause tool to pick from the description.

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?

Usage is only implied by the operation name; there is no explicit when-to-use/when-not, no mention of resuming or restarting a cadence afterwards, and no disambiguation from luca_pause_cadence. The scope and idempotency notes are prerequisites rather than 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