Skip to main content
Glama
dvvincent

VergeOS MCP Server

by dvvincent

get_cluster_status

Check the overall health and operational state of your VergeOS virtualization cluster to monitor performance and identify issues.

Instructions

Get the overall cluster status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function in VergeOSAPI class that executes the tool logic by making an HTTP request to the /api/v4/cluster_status endpoint.
    async getClusterStatus() {
      return this.request("/api/v4/cluster_status");
    }
  • src/index.js:475-481 (registration)
    Tool registration in the TOOLS array, including name, description, and input schema (empty object since no params). Used by ListToolsRequestHandler.
      name: "get_cluster_status",
      description: "Get the overall cluster status",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Dispatch case in the main CallToolRequestHandler that invokes the api.getClusterStatus() when the tool is called.
    case "get_cluster_status":
      result = await api.getClusterStatus();
      break;
  • Input schema definition for the tool: an empty object since no input parameters are required.
    inputSchema: {
      type: "object",
      properties: {},
    },
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 ('Get the overall cluster status') without explaining what 'overall cluster status' entails, whether it's a read-only operation, what format the output takes, or any performance or permission considerations. This leaves significant gaps for an agent to understand the tool's behavior.

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, clear sentence with no wasted words. It's front-loaded with the core purpose and appropriately sized for a simple, parameterless tool, 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 lack of annotations and output schema, the description is incomplete. It doesn't explain what 'overall cluster status' means (e.g., health, performance, configuration), what data is returned, or how this differs from sibling tools like 'get_cluster_stats'. For a tool in a cluster management context with many siblings, more context is needed to guide proper usage.

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 no parameter documentation is needed. The description appropriately doesn't mention parameters, which is efficient and correct for a parameterless tool, earning a high baseline score.

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 verb ('Get') and resource ('overall cluster status'), making the purpose immediately understandable. However, it doesn't distinguish this tool from its sibling 'get_cluster_stats', which could provide similar cluster-related information, leaving some ambiguity about when to use one versus the other.

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 like 'get_cluster_stats' or other sibling tools. It doesn't mention prerequisites, context, or exclusions, leaving the agent to infer usage based on tool names alone.

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