Skip to main content
Glama
punkpeye

HiveFlow MCP Server

pause_flow

Pause an active automation flow in HiveFlow to temporarily halt execution for maintenance or adjustments.

Instructions

Pausa un flujo activo

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
flowIdYesID del flujo a pausar

Implementation Reference

  • The core handler function for the 'pause_flow' tool. It makes a POST request to the HiveFlow API endpoint `/api/flows/{flowId}/pause` using the configured axios client and returns a formatted success response with the flow's new status.
    async pauseFlow(args) {
      const response = await this.hiveflowClient.post(`/api/flows/${args.flowId}/pause`);
      
      return {
        content: [
          {
            type: 'text',
            text: `⏸️ Flujo pausado exitosamente.\nEstado: ${response.data.status || 'pausado'}`
          }
        ]
      };
    }
  • TypeScript version of the core handler function for the 'pause_flow' tool. Identical logic to the JS implementation: POST to HiveFlow API to pause the flow.
    private async pauseFlow(args: any) {
      const response = await this.hiveflowClient.post(`/api/flows/${args.flowId}/pause`);
      
      return {
        content: [
          {
            type: 'text',
            text: `⏸️ Flujo pausado exitosamente.\nEstado: ${response.data.status || 'pausado'}`
          }
        ]
      };
    }
  • Input schema for the pause_flow tool, defining that it requires a 'flowId' string parameter.
    inputSchema: {
      type: 'object',
      properties: {
        flowId: {
          type: 'string',
          description: 'ID del flujo a pausar'
        }
      },
      required: ['flowId']
    }
  • src/index.js:121-134 (registration)
    Registration of the pause_flow tool in the ListTools response, including name, description, and input schema.
    {
      name: 'pause_flow',
      description: 'Pausa un flujo activo',
      inputSchema: {
        type: 'object',
        properties: {
          flowId: {
            type: 'string',
            description: 'ID del flujo a pausar'
          }
        },
        required: ['flowId']
      }
    },
  • src/index.js:221-222 (registration)
    Dispatch registration in the CallToolRequestSchema switch statement that calls the pauseFlow handler.
    case 'pause_flow':
      return await this.pauseFlow(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 pauses an active flow but doesn't describe what 'pause' entails (e.g., whether it stops execution immediately, preserves state, requires specific permissions, or has side effects). 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 that directly states the tool's purpose with zero waste. It's appropriately sized and front-loaded for a simple tool with one parameter.

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

Completeness3/5

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

Given the tool's moderate complexity (a mutation operation with no annotations or output schema), the description is minimally adequate. It states what the tool does but lacks details on behavioral implications, usage context, or error conditions. It meets the bare minimum for a tool with good schema coverage but doesn't provide a complete picture.

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 description doesn't add any parameter information beyond what's in the schema. However, schema description coverage is 100% (the 'flowId' parameter is fully documented in the schema), so 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 'Pausa un flujo activo' clearly states the action (pause) and target resource (active flow) in Spanish. It's specific about what the tool does, though it doesn't explicitly differentiate from sibling tools like 'resume_flow' or 'execute_flow' beyond the obvious verb difference.

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 active), exclusions (e.g., cannot pause already paused flows), or relationships to sibling tools like 'resume_flow' or 'execute_flow'.

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