Skip to main content
Glama
Sign In
SetLuca

SetLuca

Official
by setluca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Pause a lead's rescue cadence

luca_pause_cadence
DestructiveIdempotent

Stop a lead's running rescue cadence so no further touches are sent, with an optional stored reason. Safe to call again: a paused cadence stays paused.

Instructions

Cancel a lead's running rescue cadence so no further touches are sent. Safe to call twice: a cancelled cadence stays cancelled, and only its stored time and reason update. Example: call with { leadId, reason: "lead replied elsewhere" }.

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": {
      "leadId": "<leadId>"
    },
    "name": "luca_pause_cadence"
  }
}

Input Schema

NameRequiredDescriptionDefault
leadIdYesThe lead whose cadence to pause.
reasonNoOptional operator reason, stored on the cadence.
workspaceIdNoOptional Luca workspace id override.
workspaceSlugNoOptional Luca workspace slug override.
idempotencyKeyNoReuse the same key when retrying this exact pause.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4/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, so the safety profile is covered structurally. The description still adds real value by spelling out what idempotency means in practice — a cancelled cadence stays cancelled and only its stored time and reason change — and by stating that sending stops immediately. It stops short of noting permissions requirements or what happens when no cadence is running.

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?

Two tight sentences front-load the action and effect, then the idempotency caveat. The trailing example is short and largely corroborates the schema, so it earns only marginal space but does not bloat the definition.

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?

With an output schema available and rich annotations covering safety and idempotency, the description only needs to explain intent and side effects — which it does. An agent can decide to call it, construct the required leadId, and understand the consequence of a repeat call without further reading.

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 description coverage is 100%, so all five parameters including leadId, reason, and idempotencyKey are already documented in the schema. The example call reinforces that leadId and reason are the meaningful operator inputs, but adds no format or syntax detail the schema lacks. Baseline 3 is appropriate when the schema does the heavy lifting.

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 verb and resource — 'Cancel a lead's running rescue cadence' — plus the observable effect ('no further touches are sent'). The qualifier 'rescue cadence' on a lead separates it from the generic cadence, broadcast, and drafting pause siblings without needing to name them.

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?

The example reason ('lead replied elsewhere') implies when an operator would reach for this tool, and the cancel semantics imply the intent. However, there is no explicit when-not guidance, no mention of prerequisites such as the cadence having to be running, and no routing to sibling pause tools for other resources.

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