Skip to main content
Glama
hiveflowai

HiveFlow MCP Server

Official
by hiveflowai

pause_flow

Pause an active automation flow in HiveFlow to temporarily stop execution while preserving its state for later resumption.

Instructions

Pausa un flujo activo

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
flowIdYesID del flujo a pausar

Implementation Reference

  • The main handler function for the 'pause_flow' tool. It makes a POST request to the HiveFlow API to pause the specified flow and returns a success message with the 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'}`
          }
        ]
      };
    }
  • The input schema definition for the 'pause_flow' tool as registered in the ListTools response. Requires a 'flowId' string.
    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:222-223 (registration)
    The switch case in the CallToolRequestHandler that registers and dispatches 'pause_flow' calls to the pauseFlow method.
    case 'pause_flow':
      return await this.pauseFlow(args);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('pausa') but doesn't explain what 'pausa' entails (e.g., does it stop execution immediately, save state, require permissions, or have side effects?). For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 ('Pausa un flujo activo') that directly states the tool's purpose. It is front-loaded with no unnecessary words, making it easy for an AI agent to parse quickly. Every word earns its place, achieving optimal conciseness.

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 on flows), lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like effects, permissions, or error conditions, nor does it explain return values. For a tool that modifies state, this leaves critical gaps for an AI agent to understand its full 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 input schema has 100% description coverage, with 'flowId' documented as 'ID del flujo a pausar'. The description doesn't add any meaning beyond this, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate, as the schema does the heavy lifting for parameter documentation.

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 (pausa/pause) and the target resource (un flujo activo/an active flow). It distinguishes from siblings like 'resume_flow' by specifying the opposite action. However, it doesn't explicitly differentiate from other flow management tools beyond the verb, keeping it from a perfect score.

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 a non-existent flow), or when to choose this over other flow-related tools like 'execute_flow' or 'resume_flow'. This lack of context reduces its utility for an AI agent.

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