Lockstep Core

Overview Schema Source Related Servers Discussions Admin

cmd_enhancement

Destructive

Create a new enhancement ticket, chain, and planning declaration for AI coding assistants. It starts in Planning and defines stages: Architecture, Build, Review.

Instructions

Create enhancement: ticket + chain + planning declaration.

    Pre-typed: Planning -> Architecture -> Build -> Review.
    Starts in Planning.

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_enhancement"
  }
}

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.2/5.0

Behavior4/5

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

Annotations cover the safety profile (destructiveHint=true, idempotentHint=false, openWorldHint=false), so the description's added value is the multi-entity side effect: one call creates a ticket, a chain, and a planning declaration, and the chain starts in Planning. That composite-effect disclosure is genuinely useful and not derivable from the annotations. It stops short of saying whether failures leave partial state behind.

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?

Front-loaded with the verb and the composite output, then the phase template. Four short lines, no filler; the trailing 'Starts in Planning' is slightly redundant with the phase list but harmless.

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 no explanation, and the annotations carry the safety profile, but for a destructive, non-idempotent tool that creates three linked entities the description leaves the parameter meanings and the entity/vision relationship entirely unexplained. Adequate skeleton, real 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% across three parameters (title, vision, entity), so the description carries the full burden and does not explain any of them. 'Planning declaration' and 'entity' are never connected, and the distinction between title and vision is left entirely to the caller's guess.

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 enhancement') and decomposes it into what actually gets produced: ticket + chain + planning declaration, plus the pre-typed phase sequence. This is materially clearer than a bare 'create' command and implicitly separates it from cmd_new_ticket/cmd_refactor, though it never names those siblings outright.

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 when-to-use or when-not guidance: nothing tells the agent why it would pick cmd_enhancement over cmd_new_ticket, cmd_refactor, or cmd_bug_fix, or what preconditions the caller must satisfy. The only usage-relevant content is the resulting chain shape, which is inferred rather than stated.

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