Skip to main content
Glama
punkpeye

HiveFlow MCP Server

create_flow

Create new workflows in HiveFlow automation platform through AI assistants, enabling flow management with natural language commands.

Instructions

Crea un nuevo flujo de trabajo en HiveFlow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesNombre del flujo
descriptionYesDescripción del flujo
nodesNoNodos del flujo (opcional)

Implementation Reference

  • The handler function that executes the create_flow tool logic by posting a new flow to the HiveFlow API endpoint /api/flows and returning a success message with the created flow's ID.
    async createFlow(args) {
      const response = await this.hiveflowClient.post('/api/flows', {
        name: args.name,
        description: args.description,
        nodes: args.nodes || [],
        edges: [],
        status: 'draft'
      });
      
      return {
        content: [
          {
            type: 'text',
            text: `✅ Flujo "${args.name}" creado exitosamente.\nID: ${response.data.flow._id}\nEstado: ${response.data.flow.status}`
          }
        ]
      };
    }
  • Input schema defining the parameters for the create_flow tool: required name and description (strings), optional nodes (array of objects).
    inputSchema: {
      type: 'object',
      properties: {
        name: {
          type: 'string',
          description: 'Nombre del flujo'
        },
        description: {
          type: 'string',
          description: 'Descripción del flujo'
        },
        nodes: {
          type: 'array',
          description: 'Nodos del flujo (opcional)',
          items: { type: 'object' }
        }
      },
      required: ['name', 'description']
    }
  • src/index.js:213-214 (registration)
    Registration of the create_flow handler in the switch statement within the CallToolRequestSchema handler, dispatching calls to the createFlow method.
    case 'create_flow':
      return await this.createFlow(args);
  • src/index.js:47-69 (registration)
    Tool registration in the ListToolsRequestSchema response, listing create_flow with its name, description, and schema.
    {
      name: 'create_flow',
      description: 'Crea un nuevo flujo de trabajo en HiveFlow',
      inputSchema: {
        type: 'object',
        properties: {
          name: {
            type: 'string',
            description: 'Nombre del flujo'
          },
          description: {
            type: 'string',
            description: 'Descripción del flujo'
          },
          nodes: {
            type: 'array',
            description: 'Nodos del flujo (opcional)',
            items: { type: 'object' }
          }
        },
        required: ['name', 'description']
      }
    },
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 this is a creation operation ('Crea un nuevo'), implying it's a write/mutation tool, but doesn't disclose any behavioral traits such as required permissions, whether it's idempotent, what happens on failure, or rate limits. This leaves significant gaps for an agent to understand how to use it safely and effectively.

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 fluff or redundancy. 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 write operation with 3 parameters) and the lack of annotations and output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., a flow ID or confirmation), error conditions, or behavioral context needed for safe invocation, leaving the agent with insufficient information.

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 all parameters ('name', 'description', 'nodes') well-documented in the schema. The description adds no additional meaning about parameters beyond what's in the schema, such as format constraints or examples. This meets the baseline of 3 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 clearly states the action ('Crea un nuevo flujo de trabajo') and the resource ('en HiveFlow'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its siblings like 'execute_flow' or 'pause_flow', which would require mentioning it's specifically for creation rather than execution or management.

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., needing authentication or specific permissions), when not to use it, or how it relates to sibling tools like 'list_flows' (for viewing) or 'execute_flow' (for running).

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