Skip to main content
Glama
punkpeye

HiveFlow MCP Server

resume_flow

Resume a paused automation flow in HiveFlow by providing the flow ID, allowing users to restart interrupted processes and continue workflow execution.

Instructions

Reanuda un flujo pausado

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
flowIdYesID del flujo a reanudar

Implementation Reference

  • Executes the resume_flow tool by sending a POST request to /api/flows/{flowId}/resume endpoint of HiveFlow API and returns a formatted success message with the flow status.
    async resumeFlow(args) {
      const response = await this.hiveflowClient.post(`/api/flows/${args.flowId}/resume`);
      
      return {
        content: [
          {
            type: 'text',
            text: `▶️ Flujo reanudado exitosamente.\nEstado: ${response.data.status || 'activo'}`
          }
        ]
      };
    }
  • src/index.js:135-148 (registration)
    Registers the 'resume_flow' tool in the ListTools response, including its name, description, and input schema requiring 'flowId'.
    {
      name: 'resume_flow',
      description: 'Reanuda un flujo pausado',
      inputSchema: {
        type: 'object',
        properties: {
          flowId: {
            type: 'string',
            description: 'ID del flujo a reanudar'
          }
        },
        required: ['flowId']
      }
    },
  • TypeScript version of the resume_flow tool handler, identical logic to JS implementation.
    private async resumeFlow(args: any) {
      const response = await this.hiveflowClient.post(`/api/flows/${args.flowId}/resume`);
      
      return {
        content: [
          {
            type: 'text',
            text: `▶️ Flujo reanudado exitosamente.\nEstado: ${response.data.status || 'activo'}`
          }
        ]
      };
    }
  • src/index.ts:145-158 (registration)
    TypeScript version of the tool registration for 'resume_flow', matching the JS counterpart.
    {
      name: 'resume_flow',
      description: 'Reanuda un flujo pausado',
      inputSchema: {
        type: 'object',
        properties: {
          flowId: {
            type: 'string',
            description: 'ID del flujo a reanudar'
          }
        },
        required: ['flowId']
      }
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the action (resume) but doesn't disclose behavioral traits like whether this requires specific permissions, if it's idempotent, what happens if the flow isn't paused, or what the response looks like. For a mutation tool with zero annotation coverage, this is a significant gap.

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, efficient sentence in Spanish ('Reanuda un flujo pausado') that directly states the purpose. It's appropriately sized and front-loaded with zero wasted words, making it easy to parse quickly.

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 this is a mutation tool (resume operation) with no annotations and no output schema, the description is incomplete. It doesn't explain what happens after resuming, potential side effects, error conditions, or return values. For a tool that changes state, more context is needed.

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% (the flowId parameter is fully described in the schema as 'ID del flujo a reanudar'). The description doesn't add any additional meaning beyond what the schema provides about parameters. Baseline 3 is appropriate when the schema does the heavy lifting.

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 'Reanuda un flujo pausado' clearly states the action (reanudar/resume) and target resource (flujo pausado/paused flow). It distinguishes from siblings like pause_flow, execute_flow, and get_flow by specifying it operates on paused flows. However, it doesn't explicitly mention what type of flow (e.g., workflow, data flow) or system context.

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. It doesn't mention prerequisites (e.g., the flow must be in a paused state), when not to use it, or clarify differences from execute_flow (which might start a new execution versus resuming an existing one).

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/punkpeye/hiveflow-mcp-server'

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