Skip to main content
Glama

restart_workflow

Restart a workflow execution from the beginning using the same input parameters. This creates a new execution, optionally with the latest workflow definition.

Instructions

Restart a workflow execution from the beginning. This creates a new execution with the same input.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflowIdYesThe workflow execution ID to restart
useLatestDefinitionNoUse the latest workflow definition (default: false)

Implementation Reference

  • Handler for the 'restart_workflow' tool. Makes a POST request to Conductor's /workflow/{workflowId}/restart endpoint with optional useLatestDefinitions parameter and returns the new workflow ID.
    case "restart_workflow": {
      const { workflowId, useLatestDefinition = false } = args as any;
      const response = await conductorClient.post(
        `/workflow/${workflowId}/restart`,
        null,
        {
          params: { useLatestDefinitions: useLatestDefinition },
        }
      );
      
      return {
        content: [
          {
            type: "text",
            text: `Workflow restarted successfully. New Workflow ID: ${response.data}`,
          },
        ],
      };
    }
  • Input schema definition for the 'restart_workflow' tool, specifying required workflowId and optional useLatestDefinition.
      name: "restart_workflow",
      description:
        "Restart a workflow execution from the beginning. This creates a new execution with the same input.",
      inputSchema: {
        type: "object",
        properties: {
          workflowId: {
            type: "string",
            description: "The workflow execution ID to restart",
          },
          useLatestDefinition: {
            type: "boolean",
            description: "Use the latest workflow definition (default: false)",
          },
        },
        required: ["workflowId"],
      },
    },
  • src/index.ts:598-602 (registration)
    Registration of all tools including 'restart_workflow' via the ListToolsRequestHandler which returns the tools array.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools,
      };
    });
Behavior2/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 mentions that restarting creates a new execution, which implies mutation, but lacks details on permissions, side effects, error handling, or what happens to the original execution. This is inadequate for a mutation tool with zero annotation coverage.

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 two concise sentences with zero waste, front-loading the core action and efficiently explaining the outcome. Every sentence earns its place by adding value without redundancy.

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 complexity of a mutation tool with no annotations and no output schema, the description is incomplete. It lacks information on behavioral traits like permissions, side effects, or response format, leaving significant gaps for an AI agent to understand how to use it correctly.

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 100%, so the schema fully documents both parameters. The description adds no additional meaning beyond what the schema provides, such as clarifying parameter interactions or usage examples, which aligns with the baseline score when schema does the heavy lifting.

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 specific action ('Restart a workflow execution from the beginning') and the resource ('workflow execution'), distinguishing it from siblings like 'retry_workflow' or 'resume_workflow' by emphasizing it creates a new execution rather than continuing an existing one.

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 provides no guidance on when to use this tool versus alternatives like 'retry_workflow' or 'resume_workflow', nor does it mention prerequisites or exclusions. It states what the tool does but not when it's appropriate.

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/opensensor/conductor-mcp'

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