Lockstep Core

by dandelionrosegroup

Overview Schema Source Related Servers Discussions Admin

Python

Local

pause_chain

DestructiveIdempotent

Suspend a tracked project chain to preserve its state and signal the work is not abandoned, so it can resume later.

Instructions

Pause chain — preserves state, signals 'not abandoned'. Idempotent.

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": {
      "params": "<params>"
    },
    "name": "pause_chain"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Sep 13, 2026

TDQS

B3.1/5.0

Behavior3/5

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

'Idempotent' merely restates the idempotentHint annotation, but 'preserves state, signals not abandoned' adds semantic context about the effect of the call. It does not explain the destructiveHint=true annotation or what exactly changes, so the addition is partial.

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?

A single short, front-loaded fragment with no filler; the key semantics come first. It is tight, though terse enough to leave meaning implicit.

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

Completeness2/5

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

In a 40+ sibling lifecycle ecosystem, an agent needs to know how pause differs from archive_chain, complete_chain, and set_chain_status. With no output-schema burden (output schema exists), the description could have used that space for lifecycle routing but does not.

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 0% for the single required parameter chain_id, and the description offers nothing about its expected format, source, or constraints. The description must compensate here and does not.

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+resource ('Pause chain') that an agent can immediately contrast with resume_chain and the other chain-lifecycle siblings. No sibling is named explicitly, but the operation is unambiguous.

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?

'signals "not abandoned"' hints at the intent behind pausing (versus closing/archiving), which is real guidance. However, it never says when to choose pause_chain over archive_chain, complete_chain, or set_chain_status, nor states prerequisites.

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