Skip to main content
Glama
hiveflowai

HiveFlow MCP Server

Official
by hiveflowai

resume_flow

Resume a paused automation flow in HiveFlow by providing the flow ID to restart execution.

Instructions

Reanuda un flujo pausado

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
flowIdYesID del flujo a reanudar

Implementation Reference

  • The main handler function for the 'resume_flow' tool. It sends a POST request to the HiveFlow API to resume the specified flow and returns a success message with the new 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'}`
          }
        ]
      };
    }
  • Input schema for the 'resume_flow' tool, defining that it requires a 'flowId' string parameter.
    inputSchema: {
      type: 'object',
      properties: {
        flowId: {
          type: 'string',
          description: 'ID del flujo a reanudar'
        }
      },
      required: ['flowId']
    }
  • src/index.js:136-149 (registration)
    Tool registration in the ListToolsRequestSchema handler, defining the name, description, and input schema for 'resume_flow'.
    {
      name: 'resume_flow',
      description: 'Reanuda un flujo pausado',
      inputSchema: {
        type: 'object',
        properties: {
          flowId: {
            type: 'string',
            description: 'ID del flujo a reanudar'
          }
        },
        required: ['flowId']
      }
    },
  • src/index.js:224-225 (registration)
    Dispatch case in the CallToolRequestSchema handler that routes 'resume_flow' calls to the resumeFlow method.
    case 'resume_flow':
      return await this.resumeFlow(args);
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 tool resumes a paused flow but doesn't disclose any behavioral traits such as permissions required, side effects, error conditions, or what happens if the flow isn't paused. This is a significant gap 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 a single, efficient sentence in Spanish that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy for an agent 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 the tool's complexity (a mutation operation to resume flows), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what happens upon resumption, potential errors, or return values. For a tool with behavioral implications, more context is needed to guide the agent effectively.

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 input schema has 100% description coverage, with the single parameter 'flowId' documented as 'ID del flujo a reanudar'. The description doesn't add any additional meaning beyond this, such as format examples or constraints. Since schema coverage is high, the baseline score of 3 is appropriate, as 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/flow). It distinguishes from siblings like pause_flow, execute_flow, and get_flow by specifying it resumes paused flows. However, it doesn't explicitly mention it's for paused flows only versus other states, which slightly reduces specificity.

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 execute_flow or create_flow. It doesn't mention prerequisites (e.g., the flow must be paused) or exclusions. The context is implied but not explicit, leaving the agent to infer usage from the name and description alone.

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

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