local-agent-mcp

Overview Schema Source Related Servers Discussions Admin

Create workflow step

create_step

Idempotent

Add an immutable executable step to an existing workflow. Supply workflow ID, position, name, executor kind, and spec to define a step's action within the workflow.

Instructions

Create an immutable executable Step inside one Workflow.

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": {
      "workflow_id": "<workflow_id>",
      "position": "<position>",
      "name": "<name>",
      "executor_kind": "<executor_kind>",
      "spec": "<spec>"
    },
    "name": "create_step"
  }
}

Input Schema

Name	Required	Default
`name`	Yes
`spec`	Yes
`position`	Yes
`workflow_id`	Yes
`write_scope`	No	read_only
`executor_kind`	Yes
`worktree_path`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Aug 24, 2026

TDQS

C2.9/5.0

Behavior4/5

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

The description adds 'immutable' and 'executable' beyond what annotations convey. It clarifies that the created step is immutable and executable, which is not evident from readOnlyHint=false or idempotentHint=true. This is valuable behavioral context not present in structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise and front-loaded, but it is too terse to be useful. It omits critical parameters and usage context, so brevity comes at the expense of completeness.

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?

Given the tool's complexity (7 parameters, nested objects, output schema) and the absence of schema descriptions, this one-sentence description is severely incomplete. It lacks parameter explanations, usage guidance, and behavioral details beyond immutability, leaving agents to rely on trial and error.

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

Parameters1/5

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

Schema description coverage is 0%, and the description provides zero explanation of any of the 7 parameters (workflow_id, position, name, executor_kind, spec, write_scope, worktree_path). The enum values and nested spec object are entirely undocumented, leaving agents to guess at required semantics.

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?

The description states a clear verb ('Create') and a specific resource ('immutable executable Step inside one Workflow'), which distinguishes it from broader tools like 'create_workflow'. It doesn't contrast with sibling step-related tools (e.g., 'start_step') but the core purpose 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 Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'start_step' or 'create_workflow'. The description only states what it does, not when to invoke it or prerequisites like having an existing workflow.

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