Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Coolify: Create application env

coolify_create_application_env
Destructive

Create an environment variable for a Coolify application, with options for runtime, buildtime, preview, literal, multiline, and one-time visibility settings.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
keyYes
siteYes
uuidYes
valueYes
commentNo
is_literalNo
is_previewNo
is_runtimeNo
is_buildtimeNo
is_multilineNo
is_shown_onceNo

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 readOnlyHint=false, destructiveHint=true and idempotentHint=false, so the safety profile is partly covered. The description adds nothing about the destructive/non-idempotent nature (e.g. duplicate creates), how sensitive values are handled (is_shown_once), or what side effects occur on the application's runtime/build. For a mutation tool this is a significant gap.

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?

The single sentence is front-loaded and free of rambling, but the '[UNIFIED]' prefix is boilerplate noise and the sentence is too terse to earn its place for an 11-parameter mutation tool.

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

Completeness1/5

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

With 11 parameters, no output schema and destructive semantics, the description should explain the boolean flags, scope of the variable, and failure modes. One generic sentence leaves an agent unable to call this correctly beyond the four required string fields.

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?

The tool has 11 parameters with 0% schema description coverage, and the description mentions none of them. Semantics of is_literal, is_preview, is_runtime, is_buildtime, is_multiline and is_shown_once — all critical to correct invocation — are entirely undocumented.

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 ('Create an environment variable for a Coolify application'), so the agent knows exactly what operation is performed. It does not distinguish itself from siblings such as coolify_create_service_env or coolify_update_application_env, but the resource scope 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 guidance on when to use this versus updating an existing variable or creating a service-level variable, and no prerequisites (application must exist, key uniqueness, what happens on duplicate keys) are mentioned. The agent must infer usage entirely from the 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