Skip to main content
Glama
dvvincent

VergeOS MCP Server

by dvvincent

list_nodes

Retrieve all nodes in a VergeOS cluster to monitor infrastructure, manage virtualization resources, and administer tenant operations.

Instructions

List all nodes in the VergeOS cluster

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function in VergeOSAPI class that lists cluster nodes by making an authenticated API request to /api/v4/nodes?fields=most.
    async listNodes() {
      return this.request("/api/v4/nodes?fields=most");
    }
  • src/index.js:453-459 (registration)
    Tool registration entry in the TOOLS array, defining the tool name, description, and input schema (no parameters required). This list is returned by listTools handler.
      name: "list_nodes",
      description: "List all nodes in the VergeOS cluster",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Dispatch case in the main CallToolRequestSchema handler that calls the listNodes implementation when the tool is invoked.
    case "list_nodes":
      result = await api.listNodes();
      break;
  • Identical handler implementation in the HTTP+SSE server variant.
    async listNodes() { return this.request("/api/v4/nodes?fields=most"); }
  • Compact tool registration in the HTTP server TOOLS array.
    { name: "list_nodes", description: "List cluster nodes", inputSchema: { type: "object", properties: {} } },
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 tool lists nodes but doesn't cover aspects like pagination, rate limits, authentication needs, or what the output format might be. This leaves significant gaps for an agent to understand how to interact with the tool 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, direct sentence that front-loads the core purpose without any wasted words. It efficiently communicates what the tool does, making it easy for an agent to parse and understand quickly.

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 simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate but lacks depth. It doesn't address behavioral aspects like output format or usage context, which could be important for an agent to operate correctly in a cluster environment with multiple related tools.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here, and it implies no filtering or arguments are required, aligning well with the schema.

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 ('List') and resource ('all nodes in the VergeOS cluster'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_node_stats' or 'get_cluster_status', which might provide overlapping or related information about nodes.

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. With siblings like 'get_node_stats' and 'get_cluster_status' that might offer node-related data, the description lacks any context about use cases, prerequisites, or comparisons to help an agent choose appropriately.

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/dvvincent/vergeos-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server