local-agent-mcp

Overview Schema Source Related Servers Discussions Admin

Start workflow step

start_step

Idempotent

Initiate a specific workflow step by supplying workflow ID, step ID, and attempt number, or retrieve the existing job for that step.

Instructions

Start one explicit Step attempt or return its existing Job.

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>",
      "step_id": "<step_id>",
      "attempt": "<attempt>"
    },
    "name": "start_step"
  }
}

Input Schema

Name	Required	Description	Default
`attempt`	Yes
`step_id`	Yes
`workflow_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Aug 24, 2026

TDQS

A3.5/5.0

Behavior4/5

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

The description adds behavioral context beyond annotations by explaining what idempotentHint means in practice: it either starts a new attempt or returns the existing Job. This clarifies the side-effect profile and aligns with the openWorldHint annotation, though it does not elaborate on external side effects or authentication requirements.

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

Conciseness5/5

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

The description is a single, compact sentence with no filler. It front-loads the core action and the alternative return value, making it highly efficient. No unnecessary words or clauses.

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 has 3 required parameters and zero schema descriptions, the description is severely incomplete. It does not explain the parameters, nor does it provide any guidance on when to choose this over siblings. Although an output schema exists, the missing parameter semantics and usage guidance leave the description inadequate for an agent to call it correctly.

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?

With 0% schema description coverage, the description carries the full burden of explaining parameters, but it does not mention workflow_id, step_id, or attempt at all. The schema only provides titles, which are insufficient. The description fails to add any meaning to the parameters.

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?

The description uses a specific verb 'Start' and identifies the resource 'Step attempt', and adds the key behavior 'or return its existing Job'. This clearly distinguishes it from sibling tools like start_codex_job which deal with codex jobs, making the tool's purpose 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?

The description implies when to use the tool (to start a step attempt or retrieve an existing job) but does not explicitly mention alternatives or state when not to use it. There is no exclusions or comparison against siblings, so usage context is only implied.

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