Skip to main content
Glama
sandraschi

Robotics MCP Server

workflow_management

Manage robotic workflows to create, execute, and monitor automated processes for physical and virtual robots in the Robotics MCP Server.

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)

Args: operation: Operation to perform workflow_id: Workflow identifier workflow_data: Workflow definition (for create/update/import) variables: Variables for workflow execution execution_id: Execution identifier (for status operations) category: Filter by category (for list operation) tags: Filter by tags (for list operation) search: Search query (for list operation)

Returns: Operation-specific result with workflow data or execution status

Examples: # Create workflow workflow_management( operation="create", workflow_data={ "name": "VRoid to VRChat", "category": "avatar", "steps": [...] } )

# List workflows
workflow_management(operation="list", category="avatar")

# Execute workflow
workflow_management(
    operation="execute",
    workflow_id="workflow-123",
    variables={"vroid_file_path": "/path/to/vroid.vroid"}
)

# Get execution status
workflow_management(operation="status", execution_id="exec-456")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYes
workflow_idNo
workflow_dataNo
variablesNo
execution_idNo
categoryNo
tagsNo
searchNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does well by listing all operations and their required parameters, and includes examples showing how to use the tool. However, it doesn't disclose important behavioral traits like whether operations are idempotent, what permissions are required, rate limits, or error handling for invalid operations.

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 well-structured with clear sections (OPERATIONS, Args, Returns, Examples) but is quite lengthy. While all content is valuable given the tool's complexity, some information could be more efficiently presented. The front-loaded 'Comprehensive workflow management operations' is good, but the detailed operation list could be more concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's high complexity (8 parameters, 14 operation types) and 0% schema description coverage, the description does an excellent job of providing operational details, parameter explanations, and examples. The presence of an output schema means the description doesn't need to explain return values. However, it could better address the tool's relationship to sibling robotics tools.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by providing a comprehensive 'Args' section that explains each parameter's purpose, and the 'OPERATIONS' section clearly shows which parameters are required for each operation. This adds significant meaning beyond what the bare input schema provides, making the parameter semantics completely clear.

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 clearly states the tool performs 'Comprehensive workflow management operations' and lists 10 specific operations with their required parameters. This provides a specific verb+resource combination, though it doesn't explicitly distinguish this from sibling tools like 'robot_behavior' or 'vbot_crud' which might also manage workflows in different contexts.

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 provides implied usage guidance through the 'OPERATIONS' section that shows which parameters are required for each operation. However, it doesn't explicitly state when to use this tool versus the sibling tools, nor does it provide context about workflow management versus robot management or other alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sandraschi/robotics-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server