Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Coolify: Create service env

coolify_create_service_env
Destructive

Create an environment variable for a Coolify service by specifying its site, UUID, key, and value, with optional preview and compose override flags.

Instructions

[UNIFIED] Create an environment variable for 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>",
      "key": "<key>",
      "value": "<value>"
    },
    "name": "coolify_create_service_env"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
siteYes
uuidYes
valueYes
is_previewNo
allow_compose_environment_overrideNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=false, so the safety profile is known. The description adds nothing beyond the bare verb: it does not say what happens when the key already exists, whether the value is secret/masked, or why a create operation is flagged destructive (presumably the compose override).

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; the only waste is the cryptic "[UNIFIED]" tag that conveys no actionable meaning to an agent.

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, non-idempotent mutation with 6 undocumented parameters and no output schema, a one-line description is far too thin. An agent cannot confidently supply the two boolean flags or predict duplicate-key behavior from this definition.

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% across 6 parameters, so the description carries the full burden and fails: it only vaguely gestures at key/value/service. The non-obvious flags is_preview and allow_compose_environment_override are completely unexplained, and the distinction between 'site' and 'uuid' is left to guesswork.

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 ("Create an environment variable for a Coolify service"), which distinguishes it from the update/delete env siblings by verb alone. However, the "[UNIFIED]" prefix is unexplained and the description does nothing to differentiate it from siblings like coolify_create_application_env beyond the word "service".

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 guidance on when to use this tool versus coolify_update_service_env, coolify_update_service_envs_bulk, or the application-level equivalents. No prerequisites (e.g., whether the service must exist, whether the key must be unique) are stated.

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