Robotics MCP Server

workflow_management

Define, manage, and execute robot workflows with operations for creating, reading, updating, deleting, listing, running, and checking status. Import and export workflow definitions for reuse.

Instructions

Comprehensive workflow management operations.

OPERATIONS:

create: Create new workflow (requires workflow_data)
read: Get workflow details (requires workflow_id)
update: Update workflow (requires workflow_id, workflow_data)
delete: Delete workflow (requires workflow_id)
list: List all workflows (filterable by category, tags, search)
execute: Execute workflow (requires workflow_id, variables)
status: Get execution status (requires execution_id)
templates: List available workflow templates
import: Import workflow from JSON (requires workflow_data)
export: Export workflow to JSON (requires workflow_id)

Input Schema

TableJSON Schema

Name	Required	Description
`tags`	No	Filter by tags (for list operation)
`search`	No	Search query (for list operation)
`category`	No	Filter by category (for list operation)
`operation`	Yes	Operation to perform
`variables`	No	Variables for workflow execution
`debug_mode`	No
`workflow_id`	No	Workflow identifier
`execution_id`	No	Execution identifier (for status operations)
`workflow_data`	No	Workflow definition (for create/update/import)

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv0.2.1Aug 24, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / category / description
```
Added value: +"Filter by category (for list operation)"
```
- addedInput schema / properties / debug_mode
```
Added value: +{
+  "default": false,
+  "type": "boolean"
+}
```
- addedInput schema / properties / execution_id / description
```
Added value: +"Execution identifier (for status operations)"
```
- addedInput schema / properties / operation / description
```
Added value: +"Operation to perform"
```
- addedInput schema / properties / search / description
```
Added value: +"Search query (for list operation)"
```
- addedInput schema / properties / tags / description
```
Added value: +"Filter by tags (for list operation)"
```
- addedInput schema / properties / variables / description
```
Added value: +"Variables for workflow execution"
```
- addedInput schema / properties / workflow_data / description
```
Added value: +"Workflow definition (for create/update/import)"
```
- addedInput schema / properties / workflow_id / description
```
Added value: +"Workflow identifier"
```
Addedv1.0.0Jan 4, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description shoulders the burden of behavioral disclosure. It lists operations like delete, execute, import, and export but does not warn about side effects, destructiveness, execution costs, permissions, or consequences. The word 'Comprehensive' implies full coverage, but pause, resume, step, and continue operations from the schema are omitted, making it less transparent.

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?

The description is reasonably concise and well-structured, using a bullet list of operations that is easy to scan. The first line 'Comprehensive workflow management operations' is slightly redundant, but it does not waste much space. The main issue is that the structure suggests completeness while four enum operations (pause, resume, step, continue) are missing.

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?

This is a multi-operation, 9-parameter tool with no annotations, so the description needs to be thorough. It omits pause, resume, step, and continue, which are valid operations in the schema, and doesn't address debug_mode. The operation list is useful but not complete enough for an agent to safely and correctly invoke all possible behavior.

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

Parameters3/5

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

Schema description coverage is 89%, which is high enough to set the baseline at 3. The description does reinforce operation-parameter mapping, e.g., 'execute: requires workflow_id, variables', but this adds little beyond the schema's own parameter descriptions, which already say 'for status operations', 'for list operation', and 'for create/update/import'. It does not explain debug_mode or the omitted operations in the enum.

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 the tool's domain and enumerates specific operations: create, read, update, delete, list, execute, status, templates, import, export. Each operation is a clear verb plus resource, so an agent can understand what the tool does. However, it does not differentiate from sibling tools by naming what it is not or when to prefer it.

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 gives an operation list and required parameters ('requires workflow_id'), but does not provide guidance on when to use this tool instead of a sibling tool, nor any exclusion or alternative recommendations. The usage context is only implicit: if you need workflow management, use it.

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