Skip to main content
Glama
dvvincent

VergeOS MCP Server

by dvvincent

list_tenants

Retrieve a list of all tenants in the VergeOS virtualization platform to manage tenant administration and monitor cluster resources.

Instructions

List all tenants in VergeOS

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function in the VergeOSAPI class that implements the list_tenants tool by making an API request to fetch tenants from VergeOS.
    async listTenants() {
      return this.request("/api/v4/tenants?fields=most");
    }
  • The tool schema definition for list_tenants, including name, description, and empty input schema (no parameters required). Used for tool listing and validation.
    {
      name: "list_tenants",
      description: "List all tenants in VergeOS",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • src/index.js:576-577 (registration)
    The dispatch/registration in the CallToolRequestSchema handler where list_tenants tool calls are routed to the api.listTenants() implementation.
    case "list_tenants":
      result = await api.listTenants();
  • Identical handler implementation in the HTTP server variant of the MCP server.
    async listTenants() {
      return this.request("/api/v4/tenants?fields=most");
    }
  • Handler in the advanced MCP HTTP+SSE server variant.
    async listTenants() { return this.request("/api/v4/tenants?fields=most"); }
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. It states it lists all tenants but doesn't mention any behavioral traits like pagination, rate limits, permissions required, or what 'all tenants' means in practice (e.g., active only, includes deleted). This leaves significant gaps for an agent.

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 that directly states the tool's purpose without any fluff. It's appropriately sized and front-loaded, making it easy 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 no annotations, no output schema, and a simple list operation, the description is incomplete. It doesn't explain what the output contains (e.g., tenant IDs, names, statuses) or any behavioral context like ordering or limitations, leaving the agent with insufficient information for reliable use.

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 the schema fully documents the lack of inputs. The description doesn't need to add parameter semantics, and it doesn't contradict the schema. Baseline is 4 for zero parameters.

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 all') and resource ('tenants in VergeOS'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_tenant' or 'tenant_action', which would require more specific scope or context.

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_tenant' (for a specific tenant) or 'tenant_action' (for performing actions on tenants). There's no mention of prerequisites, context, or exclusions.

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