Skip to main content
Glama
dvvincent

VergeOS MCP Server

by dvvincent

tenant_action

Control tenant power states in VergeOS by performing actions like power on, power off, reset, or isolation toggles using tenant ID.

Instructions

Perform an action on a tenant (poweron, poweroff, reset)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTenant ID
actionYesAction to perform

Implementation Reference

  • Core handler function in VergeOSAPI class that executes the tenant_action by proxying a POST request to the /api/v4/tenant_actions endpoint with the tenant ID and action payload.
    async tenantAction(id, action) {
      return this.request("/api/v4/tenant_actions", {
        method: "POST",
        headers: { "Content-Type": "application/json" },
        body: JSON.stringify({ tenant: id, action }),
      });
    }
  • src/index.js:431-449 (registration)
    Tool registration in the TOOLS array, defining the name, description, and input schema for tenant_action, used in list_tools response.
    {
      name: "tenant_action",
      description: "Perform an action on a tenant (poweron, poweroff, reset)",
      inputSchema: {
        type: "object",
        properties: {
          id: {
            type: "number",
            description: "Tenant ID",
          },
          action: {
            type: "string",
            enum: ["poweron", "poweroff", "reset", "isolateon", "isolateoff"],
            description: "Action to perform",
          },
        },
        required: ["id", "action"],
      },
    },
  • Dispatch handler in the MCP call_tool request handler that invokes the tenantAction method with parsed arguments.
    case "tenant_action":
      result = await api.tenantAction(args.id, args.action);
      break;
  • The dispatch case in the tool execution switch statement.
    case "tenant_action":
      result = await api.tenantAction(args.id, args.action);
      break;
Behavior2/5

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

With no annotations, the description carries full burden but lacks critical behavioral details. It implies mutation (poweron/poweroff/reset) but doesn't disclose permissions needed, side effects, reversibility, or error conditions. For a tool that modifies tenant state, this is a significant gap.

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. It front-loads the core purpose and lists action types clearly, making it easy to parse.

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 mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'tenant' means in this context, the effects of actions, or what to expect upon success/failure. Given the complexity and lack of structured data, more context is needed.

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?

Schema description coverage is 100%, so the schema fully documents both parameters (id as tenant ID, action with enum values). The description adds no additional parameter semantics beyond what's in the schema, meeting the baseline for high coverage.

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 ('perform') and resource ('tenant'), specifying the action types (poweron, poweroff, reset). It distinguishes from most siblings that are 'get' or 'list' operations, though it doesn't explicitly differentiate from similar mutation tools like network_action or power_on_vm.

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?

No guidance on when to use this tool versus alternatives like power_on_vm or reset_vm is provided. The description only lists actions without context about prerequisites, timing, 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