local-agent-mcp

by ezra-y

Overview Schema Source Related Servers Discussions Admin

Python

Local

Create workflow

create_workflow

Create durable workflows for multi-step tasks, enabling structured execution and management of complex operations.

Instructions

Create a durable Workflow for a multi-Step task.

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": {
      "project": "<project>",
      "title": "<title>"
    },
    "name": "create_workflow"
  }
}

Input Schema

Name	Required	Description	Default
`title`	Yes
`project`	Yes
`metadata`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Aug 24, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already indicate readOnlyHint=false, so the write nature is known. The description adds 'durable', hinting at persistence, which is additional context not in annotations. However, it does not disclose behavior like side effects, failure modes, or whether the workflow is immediately executable. It adds some value but not rich behavioral detail, consistent with the lower bar set by annotations.

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 concise sentence that immediately states the core purpose. There is zero redundancy or filler. It is front-loaded with the main action and scoping qualifier. Without the need for more length due to its minimalism, this is efficient.

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?

Despite having an output schema, the description lacks essential context. It does not explain what constitutes a 'multi-Step task', how the workflow relates to steps, whether the workflow is created in a draft state, or any preconditions like project existence. For a create operation with three parameters, the description is far from complete. An agent would struggle to know the full context without additional investigation.

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 must compensate by explaining the meaning, constraints, or format of parameters. It does not mention any of title, project, or metadata. The schema provides only names and types, but the description adds nothing about their purpose, relationship, or potential values. This is a significant gap.

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 clearly states the verb 'Create', the resource 'Workflow', and adds the qualifier 'durable for a multi-Step task'. This distinguishes it from sibling tools like create_step (which likely creates a single step) and get_workflow (which reads). It is specific and non-tautological.

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?

The description implies usage for creating a multi-step workflow but provides no explicit guidance on when to choose this over alternatives, nor does it mention exclusions or prerequisites. It lacks any 'when not to use' or comparison to siblings like create_step or start_step. The single sentence leaves the selection logic entirely to the agent's inference.

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