Skip to main content
Glama
dvvincent

VergeOS MCP Server

by dvvincent

list_volumes

Retrieve all storage volumes from VergeOS virtualization platforms to manage storage resources and monitor capacity across clusters.

Instructions

List all storage volumes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function in VergeOSAPI class that implements the list_volumes tool by calling the VergeOS API endpoint for volumes.
    async listVolumes() {
      return this.request("/api/v4/volumes?fields=most");
    }
  • Handler method in the HTTP MCP server implementation that fetches storage volumes via API request.
    async listVolumes() { return this.request("/api/v4/volumes?fields=most"); }
  • Direct API handler for list_volumes in the local-proxy direct connection mode.
    async function listVolumes() { return apiRequest("/api/v4/volumes?fields=most"); }
  • src/index.js:493-499 (registration)
    Tool registration in the TOOLS array including schema, name, and description for the MCP server.
      name: "list_volumes",
      description: "List all storage volumes",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Switch case registration in executeTool function that maps tool call to the handler.
    case "list_volumes": return api.listVolumes();
    case "get_logs": return api.getLogs({ limit: args?.limit || 50, level: args?.level, object_type: args?.object_type });
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 action ('List') but doesn't describe what 'List' entails—whether it returns a summary or detailed data, if it's paginated, requires authentication, has rate limits, or affects system state. For a tool with zero annotation coverage, this is insufficient behavioral context.

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 with zero waste: 'List all storage volumes'. It is front-loaded and appropriately sized for a simple tool, making it easy to parse quickly. Every word earns its place by specifying the action and resource.

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 but incomplete. It lacks context on return values, behavioral traits, or usage scenarios. For even a simple tool, more detail on what 'List' returns or system impact would improve completeness, especially with no annotations to fill gaps.

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, meaning there are no parameters to document. The description doesn't need to add parameter semantics beyond what the schema provides. A baseline of 4 is appropriate as the description implies no filtering or options, aligning with the empty 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 'List all storage volumes' clearly states the verb ('List') and resource ('storage volumes'), making the purpose immediately understandable. It distinguishes from siblings like 'list_networks' or 'list_vms' by specifying the resource type. However, it doesn't specify scope or filtering options, which prevents a perfect score.

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 sibling tools like 'get_vm_drives' that might retrieve volume information for specific VMs, there's no indication of whether this tool lists all volumes globally or per-resource. No exclusions, prerequisites, or comparison to siblings are mentioned.

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