Skip to main content
Glama

resume_workflow

Restart a paused workflow execution to continue processing from the interruption point.

Instructions

Resume a paused workflow execution. The workflow will continue from where it was paused.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflowIdYesThe workflow execution ID to resume

Implementation Reference

  • The execution handler for the 'resume_workflow' MCP tool. It extracts the workflowId from input arguments, calls the Conductor REST API to resume the workflow, and returns a success confirmation message.
    case "resume_workflow": {
      const { workflowId } = args as any;
      await conductorClient.put(`/workflow/${workflowId}/resume`);
      
      return {
        content: [
          {
            type: "text",
            text: `Workflow ${workflowId} resumed successfully.`,
          },
        ],
      };
    }
  • src/index.ts:292-306 (registration)
    Tool registration entry in the MCP tools array, defining the name, description, and input schema (requiring 'workflowId') for list_tools response.
    {
      name: "resume_workflow",
      description:
        "Resume a paused workflow execution. The workflow will continue from where it was paused.",
      inputSchema: {
        type: "object",
        properties: {
          workflowId: {
            type: "string",
            description: "The workflow execution ID to resume",
          },
        },
        required: ["workflowId"],
      },
    },
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 states the workflow continues from where it was paused, which is useful, but fails to cover critical aspects such as required permissions, potential side effects, error handling, or response format. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 sentences, front-loaded with the core purpose and followed by a clarifying detail. Every word contributes directly to understanding the tool's function, with no redundant or extraneous information, making it highly 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?

Given the complexity of a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits, error conditions, return values, and differentiation from sibling tools, making it insufficient for an agent to fully understand how to use it effectively in context.

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?

The schema description coverage is 100%, with the single parameter 'workflowId' fully documented in the schema. The description does not add any additional meaning or context beyond what the schema provides, such as format examples or constraints, so it meets the baseline of 3 for high schema coverage.

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 action ('Resume') and target resource ('a paused workflow execution'), with the specific scope of continuing from where it was paused. However, it does not explicitly differentiate from siblings like 'restart_workflow' or 'retry_workflow', which might have overlapping purposes, preventing a score of 5.

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 paused workflows but provides no explicit guidance on when to use this tool versus alternatives like 'restart_workflow' or 'retry_workflow'. It lacks context on prerequisites, exclusions, or scenarios where this is the preferred choice, offering minimal direction.

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