Skip to main content
Glama
Sign In

fnlowl

by com.fnlowl
OverviewDiscussionsAdmin

Pause sequence

pause_sequence
Destructive

Move a sequence to draft, which stops new enrolments. Stopping mail is never the slower path, so this applies immediately. Starting one again is activate_sequence, which a person approves: an active sequence enrols every future lead and sends on a timer with nobody watching.

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": {
      "sequenceId": "<sequenceId>"
    },
    "name": "pause_sequence"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectNoA project id from list_projects. Runs this call in that project instead of the connection default.
sequenceIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag the tool as non-read-only and destructive. The description adds useful behavioral context: the change applies immediately, stops new enrolments, and contrasts with an active sequence that sends automatically. It does not clarify whether already-enrolled leads or queued sends are cancelled, nor what permissions are required.

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 definition is three short sentences and front-loads the action and effect. The rationale sentence is compact, though “Stopping mail is never the slower path” is slightly oblique.

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?

For a destructive mutation, the description covers the immediate effect and routes activation to a person-approved alternative. Important gaps remain around what happens to existing enrolments and queued sends, and around the required sequenceId semantics; annotations and schema partially cover safety and project scoping.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%: project is documented, but the required sequenceId has no schema description. The tool description never mentions either parameter or explains where sequenceId comes from, so it does not compensate for the undocumented required parameter.

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 sequence to draft, which stops new enrolments. It names the immediate effect and clearly distinguishes the operation from activate_sequence. An agent can identify what this tool does 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?

The description explicitly names activate_sequence as the alternative and explains that activation requires person approval and enrols future leads on a timer. It implies pause is for stopping new enrolments immediately, but it does not spell out explicit when-not conditions or prerequisites.

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

All fnlowl toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources