Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Coolify: Delete application env

coolify_delete_application_env
Destructive

Remove an environment variable from a Coolify application by specifying the site, application UUID, and environment variable UUID.

Instructions

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

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_application_env"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
uuidYes
env_uuidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

C2.9/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 structurally. The description adds nothing on top: it does not say whether deletion is permanent, whether the app must be redeployed for the change to take effect, or what the response contains — meaningful gaps for an irreversible operation.

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

Conciseness4/5

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

A single front-loaded sentence with no filler beyond the opaque "[UNIFIED]" tag. It is efficient, though its brevity comes partly from omitting necessary detail rather than from disciplined editing.

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?

Placeholder.

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

Parameters2/5

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

Schema description coverage is 0%, so all three required parameters (site, uuid, env_uuid) are undocumented. The description only loosely implies that one identifier is the application and another the env variable, and says nothing at all about `site`, leaving the ambiguity between `uuid` and `env_uuid` unresolved.

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 states a specific verb and resource ("Delete an environment variable from a Coolify application"), which clearly separates it from create/update siblings by action. The "[UNIFIED]" prefix is unexplained and adds nothing, but the core statement is unambiguous.

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?

There is no when-to-use guidance, no mention of prerequisites (does the app need to be stopped? redeployed?), and no reference to alternatives such as coolify_update_application_env for modifying rather than removing a variable. The agent must infer everything from the verb.

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