Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_servicesA

List all admin services this MCP can reach (Uptime Kuma, NPMPlus/Nginx Proxy Manager, Porkbun, Cloudflare, Docker, Proxmox), which are configured, and which named instances exist for each (e.g. multiple Docker hosts or Proxmox nodes with separate credentials). Call this first if you're unsure what's available.

list_actionsA

Search/list available actions across configured services. Returns each action's id, owning service, a one-line summary, whether it's read-only or destructive, and its JSON input schema. Use query to search by keyword (e.g. 'restart container', 'dns record', 'proxy host'); omit both filters to list everything. Only configured services' actions are returned.

execute_actionA

Execute one action against one instance of a service. Look up the action id and its params schema via list_actions first. instance selects which configured target to use (e.g. which Proxmox node or Docker host) - omit it only if the service has exactly one instance configured. Destructive actions (as flagged by list_actions) change or delete remote state - double check params before calling.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 3 tools

Disambiguation5/5

The three tools target clearly distinct phases: discovering services/instances, discovering available actions, and executing a chosen action. There is no overlap in purpose, and the descriptions reinforce the correct order of use.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern: list_services, list_actions, execute_action. The plural vs. singular noun choice is natural for listing multiple items versus executing one action.

Tool Count5/5

Three tools are well-scoped for a generic admin-action gateway: one for service discovery, one for action discovery, and one for execution. The dynamic action surface avoids tool bloat while covering the server's purpose.

Completeness5/5

The tool set provides complete lifecycle support for the gateway pattern: list services/instances, list available actions with schemas and safety flags, and execute any action against a chosen instance. No obvious operational gaps exist for the stated domain.

Maintenance

ActivityMaintained
ResponsivenessNo issues