Skip to main content
Glama
dvvincent

VergeOS MCP Server

by dvvincent

get_cluster_stats

Retrieve storage tier statistics for VergeOS virtualization clusters to monitor capacity and performance across different storage levels.

Instructions

Get cluster tier statistics (storage tiers)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function in VergeOSAPI class that executes the tool logic by requesting cluster tier stats from the VergeOS API endpoint /api/v4/cluster_tier_stats.
    async getClusterStats() {
      return this.request("/api/v4/cluster_tier_stats");
    }
  • The tool schema definition in the TOOLS array, specifying name, description, and empty input schema (no parameters required).
      name: "get_cluster_stats",
      description: "Get cluster tier statistics (storage tiers)",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • src/index.js:596-598 (registration)
    The switch case in the MCP CallToolRequestHandler that registers and routes calls to the get_cluster_stats tool to the api.getClusterStats() handler.
    case "get_cluster_stats":
      result = await api.getClusterStats();
      break;
  • Identical handler implementation in the HTTP server variant's VergeOSAPI class.
    async getClusterStats() {
      return this.request("/api/v4/cluster_tier_stats");
    }
  • Handler in the MCP HTTP+SSE server's VergeOSAPI class, same API request logic.
    async getClusterStats() { return this.request("/api/v4/cluster_tier_stats"); }
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 only states what the tool does ('Get cluster tier statistics') without any information about permissions required, rate limits, response format, or whether it's a read-only operation. For a tool with zero annotation coverage, this leaves significant gaps in understanding its 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 extremely concise ('Get cluster tier statistics (storage tiers)')—just one phrase that directly states the purpose. It's front-loaded with the core action and resource, with no wasted words or unnecessary elaboration.

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 has no parameters and no output schema, the description is minimally complete for a simple read operation. However, with no annotations to provide behavioral context and siblings that might overlap, it lacks guidance on usage and behavioral traits. It's adequate but has clear gaps in contextual information.

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 there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately doesn't mention any. A baseline score of 4 is applied since no parameters exist, and the description doesn't incorrectly imply any.

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 tool's purpose: 'Get cluster tier statistics (storage tiers)'. It specifies the verb ('Get') and resource ('cluster tier statistics'), making it unambiguous. However, it doesn't explicitly differentiate from siblings like 'get_cluster_status' or 'get_node_stats', which might also provide statistical data.

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. With siblings like 'get_cluster_status' and 'get_node_stats' that might overlap in scope, there's no indication of when this tool is appropriate or what distinguishes it from other statistical tools.

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