Skip to main content
Glama
Sign In
Secure VPS Operations MCP Server

Secure VPS Operations MCP Server

by ojoilesanmi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_containers

List approved Docker containers and their status to audit VPS container health through read-only SSH access.

Instructions

List allowlisted Docker containers and their status.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_containers"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It indicates a read-only operation ('List') and adds that it only returns 'allowlisted' containers with status, which is useful context. However, it does not explain what 'allowlisted' means or any potential failure conditions, leaving some ambiguity.

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, concise sentence that clearly states the tool's purpose. No unnecessary words or fluff, making it highly scannable and appropriately sized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (no parameters) and an output schema exists, so the description doesn't need to explain return values. The only notable gap is the undefined term 'allowlisted', which may require additional context to fully understand the tool's scope. Otherwise, it is complete for a basic listing tool.

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 and the schema has 100% coverage (empty object), so the description has no parameter details to add. According to the rubric, 0 parameters sets a baseline score of 4, and the description does not interfere with that.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses the specific verb 'List' with the resource 'Docker containers' and scope 'allowlisted', making it clear what the tool does. It also includes 'status', which distinguishes it from sibling tools like get_container_logs (which retrieves logs) and get_service_status (which checks services).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the usage scenario (when you need to see allowlisted containers and their status) but does not explicitly state when to use it over alternatives. There are no exclusions or mentions of other tools like get_container_logs, so it is not fully differentiated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools