Skip to main content
Glama
hiveflowai

HiveFlow MCP Server

Official
by hiveflowai

list_mcp_servers

Lists configured MCP servers within the HiveFlow automation platform to help users manage their connected automation tools.

Instructions

Lista los servidores MCP configurados en HiveFlow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that implements the 'list_mcp_servers' tool. It makes an API call to '/api/mcp/servers', processes the servers list, formats it as a markdown-style text response, and returns it in the MCP content format.
    async listMCPServers() {
      const response = await this.hiveflowClient.get('/api/mcp/servers');
      const servers = response.data.servers || [];
      
      const serversList = servers.map(server => 
        `• ${server.name} - Estado: ${server.status} (${server.isConnected ? 'Conectado' : 'Desconectado'})`
      ).join('\n');
      
      return {
        content: [
          {
            type: 'text',
            text: `🔌 Servidores MCP (${servers.length}):\n\n${serversList || 'No hay servidores MCP configurados'}`
          }
        ]
      };
    }
  • src/index.js:150-157 (registration)
    Registration of the 'list_mcp_servers' tool in the ListToolsRequestSchema handler. Includes name, description, and empty input schema (no parameters required).
    {
      name: 'list_mcp_servers',
      description: 'Lista los servidores MCP configurados en HiveFlow',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    },
  • src/index.js:226-227 (registration)
    Dispatch/registration case in the CallToolRequestSchema switch statement that routes calls to the listMCPServers handler method.
    case 'list_mcp_servers':
      return await this.listMCPServers();
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. It states it's a list operation, implying read-only behavior, but doesn't disclose any behavioral traits such as pagination, sorting, rate limits, authentication needs, or what happens if no servers are configured. For a 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 in Spanish that directly states the tool's purpose without any waste. It's appropriately sized and front-loaded, with every word contributing to clarity. No unnecessary details or redundancy are present.

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 simplicity (0 parameters, no output schema, no annotations), the description is minimal. It states what the tool does but lacks completeness: no output format, no behavioral context (e.g., list format, error handling), and no usage guidelines. For even a simple list tool, this leaves gaps in understanding how to effectively use it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description doesn't add parameter information beyond this, but with no parameters, a baseline of 4 is appropriate as there's nothing to compensate for. No value is added, but none is needed.

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 ('Lista los servidores MCP') and resource ('configurados en HiveFlow'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'list_flows' or 'get_flow', which also list resources but different types. The purpose is clear but lacks sibling differentiation.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention any context, prerequisites, or exclusions. With sibling tools like 'get_mcp_server' (implied but not listed) potentially existing, there's no indication of when to list all servers versus retrieve a specific one.

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