Skip to main content
Glama
punkpeye

HiveFlow MCP Server

get_flow

Retrieve details for a specific automation flow from the HiveFlow platform using its unique flow ID.

Instructions

Obtiene detalles de un flujo especĂ­fico

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
flowIdYesID del flujo

Implementation Reference

  • The handler function for the 'get_flow' tool. It makes an API request to retrieve details of a specific flow by ID and returns a formatted text summary of the flow's information.
    private async getFlow(args: any) {
      const response = await this.hiveflowClient.get(`/api/flows/${args.flowId}`);
      const flow = response.data.flow;
      
      return {
        content: [
          {
            type: 'text',
            text: `📊 Detalles del flujo "${flow.name}":\n• ID: ${flow._id}\n• Estado: ${flow.status || 'draft'}\n• Nodos: ${flow.nodes?.length || 0}\n• Descripción: ${flow.description || 'Sin descripción'}\n• Última actualización: ${flow.updatedAt || 'N/A'}`
          }
        ]
      };
    }
  • The schema definition for the 'get_flow' tool, specifying the required 'flowId' input parameter.
    {
      name: 'get_flow',
      description: 'Obtiene detalles de un flujo especĂ­fico',
      inputSchema: {
        type: 'object',
        properties: {
          flowId: {
            type: 'string',
            description: 'ID del flujo'
          }
        },
        required: ['flowId']
      }
    },
  • src/index.ts:227-228 (registration)
    The switch case that registers and routes calls to the 'get_flow' handler within the CallToolRequestSchema handler.
    case 'get_flow':
      return await this.getFlow(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 only states what the tool does ('obtiene detalles') but doesn't describe the return format, error conditions, authentication needs, rate limits, or whether it's a read-only operation. For a tool with zero annotation coverage, this is a significant gap in behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized for a simple retrieval tool, though it could be slightly more informative without sacrificing 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 lack of annotations and output schema, the description is incomplete. It doesn't explain what 'detalles' includes (e.g., flow configuration, status, metadata) or provide any behavioral context. For a retrieval tool with no structured output documentation, the description should do more to compensate for these gaps.

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-specific information beyond what's already in the schema (which has 100% coverage for the single 'flowId' parameter). The schema already describes 'flowId' as 'ID del flujo,' so the description provides no additional semantic value. This meets the baseline of 3 for high schema coverage.

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 'Obtiene detalles de un flujo especĂ­fico' clearly states the verb ('obtiene' - gets) and resource ('flujo' - flow), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'list_flows' or 'get_flow_executions' beyond the singular vs. plural distinction, which is why it doesn't reach 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 that this retrieves details for a specific flow (vs. 'list_flows' for multiple flows or 'get_flow_executions' for execution data), nor does it specify prerequisites like needing a flow ID. This leaves the agent with minimal context for tool selection.

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