Skip to main content
Glama

Coolify: Delete service env

coolify_delete_service_env
Destructive

Delete a Coolify service environment variable by providing the site, service UUID, and environment variable UUID.

Instructions

[UNIFIED] Delete an environment variable from a Coolify service.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site": "<site>",
      "uuid": "<uuid>",
      "env_uuid": "<env_uuid>"
    },
    "name": "coolify_delete_service_env"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
uuidYes
env_uuidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is covered. The description adds nothing beyond them: it does not say deletion is irreversible, whether dependent references break, or whether confirmation is needed before invoking.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short, front-loaded sentence with no wasted words, but the brevity is under-specification rather than efficiency. It reads cleanly but carries almost no information payload.

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 destructive mutation with three fully undocumented required parameters and no output schema, the description should explain parameter roles and consequences. Given that annotations carry the destructiveness signal, the remaining gap is parameter meaning, which is entirely unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for all three required parameters, and the description does not explain that 'site' is the Coolify instance, 'uuid' the service identifier, or 'env_uuid' the environment variable to remove. With no schema help and no description help, an agent cannot know what to pass.

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?

States a specific verb and resource ('Delete an environment variable from a Coolify service'), which is distinguishable from coolify_update_service_env and coolify_create_service_env by the name plus verb. The '[UNIFIED]' prefix is unexplained noise but does not obscure the core action.

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 versus coolify_delete_application_env, coolify_update_service_env, or bulk variants, and no stated prerequisites such as needing the service to exist or permissions required. The agent must infer everything from the tool name.

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