Skip to main content
Glama
dvvincent

VergeOS MCP Server

by dvvincent

get_node_stats

Retrieve performance metrics and operational statistics for a specific node in the VergeOS virtualization platform to monitor cluster health and resource utilization.

Instructions

Get statistics for a specific node

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNode ID

Implementation Reference

  • Core handler function in VergeOSAPI class that executes the HTTP request to the VergeOS backend API to fetch statistics for the specified node ID.
    async getNodeStats(id) {
      return this.request(`/api/v4/node_stats?node=${id}`);
    }
  • Tool schema definition in the TOOLS array, specifying the input schema requiring a numeric node ID.
    {
      name: "get_node_stats",
      description: "Get statistics for a specific node",
      inputSchema: {
        type: "object",
        properties: {
          id: {
            type: "number",
            description: "Node ID",
          },
        },
        required: ["id"],
      },
    },
  • Dispatch handler in the MCP CallToolRequestSchema request handler that routes the tool call to the api.getNodeStats method.
    case "get_node_stats":
      result = await api.getNodeStats(args.id);
      break;
  • src/index.js:526-528 (registration)
    Registration of the ListToolsRequestSchema handler which returns the TOOLS array including the get_node_stats tool definition.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools: TOOLS };
    });
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Get statistics' implies a read-only operation, it doesn't specify what kind of statistics are returned, whether there are rate limits, authentication requirements, or what format the statistics come in. This leaves significant behavioral gaps for a tool with no annotation coverage.

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 extremely concise at just 5 words ('Get statistics for a specific node'), with zero wasted words. It's front-loaded with the core purpose and efficiently communicates the essential information without unnecessary elaboration.

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?

For a statistics-retrieval tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what statistics are returned, their format, or any behavioral characteristics. Given the complexity of statistical data and the lack of structured output information, the description should provide more context about what 'statistics' encompasses.

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 the single parameter 'id' clearly documented as 'Node ID'. The description doesn't add any additional parameter semantics beyond what the schema provides, but with complete schema coverage, the baseline score of 3 is appropriate.

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 ('Get statistics') and target resource ('for a specific node'), which is a specific verb+resource combination. However, it doesn't distinguish itself from sibling tools like 'get_cluster_stats' or 'get_vm_status' that might provide similar statistical information for different resources.

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. There's no mention of prerequisites, when-not-to-use scenarios, or comparisons to sibling tools like 'get_cluster_stats' or 'list_nodes' that might serve related purposes.

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