Lockstep Core

Overview Schema Source Related Servers Discussions Admin

cmd_new_initiative

Destructive

Create a new initiative with a ticket and a full-funnel chain that starts in Discovery, so AI coding assistants track work from vision through review.

Instructions

Create initiative: ticket + full-funnel chain + discovery declaration.

    Pre-typed: full funnel (Discovery -> Research -> Planning ->
    Architecture -> Build -> Review). Starts in Discovery.

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": {
      "title": "<title>",
      "vision": "<vision>"
    },
    "name": "cmd_new_initiative"
  }
}

Input Schema

Name	Required	Description	Default
`title`	Yes
`entity`	No
`vision`	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/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true and non-idempotent, so the safety profile is covered. The description usefully discloses the created structure (chain with a pre-typed six-stage funnel) and the initial stage, which goes beyond annotations. It does not state that the operation is irreversible or what permissions are needed.

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, with the funnel detail following. The only minor waste is the redundant restatement that the funnel starts in Discovery immediately after listing Discovery first.

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 need not be described, and annotations cover the safety profile. What remains missing is any explanation of the three parameters (especially entity) and the irreversible nature of creating a chain, leaving the definition adequate but with clear gaps.

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% and the description says nothing about title, entity, or vision. 'Title' and 'vision' are semi-self-evident, but 'entity' is opaque and is left entirely undocumented in both schema and description, so the description fails to compensate for the coverage gap.

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 ('Create initiative') and then enumerates the composite output: ticket + full-funnel chain + discovery declaration. That is far more informative than the bare name. It does not, however, name which sibling it is not (e.g. cmd_new_ticket or create_chain), so differentiation is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance and no mention of alternatives among the many create_* / cmd_new_* siblings. The note that it 'Starts in Discovery' hints at lifecycle context but never says what condition should lead an agent here rather than to cmd_new_ticket or create_chain.

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