Skip to main content
Glama

server_manage

Destructive

Manage server lifecycle: add existing servers to local config, unregister without affecting running instances, or permanently delete from cloud provider. Supports Coolify, Dokploy, or bare servers.

Instructions

Manage Kastell servers. Actions: 'add' registers an existing Coolify or bare server to local config (validates API token, optionally verifies Coolify via SSH — pass mode:'bare' for servers without Coolify). 'remove' unregisters a server from local config only (cloud server keeps running). 'destroy' PERMANENTLY DELETES the server from the cloud provider and removes from local config. Requires provider API tokens as environment variables. Destroy is blocked when KASTELL_SAFE_MODE=true. Server mode for 'add' action: 'coolify', 'dokploy', or 'bare'. Default: coolify

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction: 'add' register an existing server, 'remove' unregister from local config (server stays running), 'destroy' permanently delete from cloud provider AND local config
serverNoServer name or IP (required for 'remove' and 'destroy' actions)
providerNoCloud provider: 'hetzner', 'digitalocean', 'vultr', 'linode' (required for 'add' action). If omitted and client supports elicitation, a form will be shown.
ipNoServer public IP address (required for 'add' action). If omitted and client supports elicitation, a form will be shown.
nameNoServer name, 3-63 chars, lowercase alphanumeric and hyphens (required for 'add' action). If omitted and client supports elicitation, a form will be shown.
skipVerifyNoSkip Coolify SSH verification when adding a server (only for 'add' action)
modeNoServer mode for 'add' action: 'coolify', 'dokploy', or 'bare'. Default: coolifycoolify

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations indicate destructiveHint=true; description adds specific behavioral details: destroy permanently deletes from cloud provider and local config, requires provider API tokens, and is blocked by safe mode. No contradictions.

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?

Description is concise (4-5 sentences), front-loaded with core purpose, then action details. Every sentence adds value with no redundancy.

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

Completeness5/5

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

Given 7 parameters, 3 enums, and output schema existence, description thoroughly covers actions, prerequisites (env vars), safety mechanisms, mode options, and action-specific parameter requirements.

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?

Schema coverage is 100% with parameter descriptions. Description adds further meaning: explains mode default and values, skipVerify only for add, server required for remove/destroy, and that some params can be omitted if client supports elicitation.

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?

Description clearly states the tool manages Kastell servers with three actions: add, remove, destroy. It differentiates from sibling server_* tools by being the CRUD management tool.

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

Usage Guidelines5/5

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

Explicitly describes when to use each action (e.g., remove unregisters locally, destroy permanently deletes from cloud), contrasts remove vs destroy, mentions blocked when KASTELL_SAFE_MODE=true, and explains mode options.

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/kastelldev/kastell'

If you have feedback or need assistance with the MCP directory API, please join our Discord server