Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Coolify: Update service envs bulk

coolify_update_service_envs_bulk
Destructive

Update multiple environment variables for a Coolify service in one request to keep service configuration consistent and reduce manual edits.

Instructions

[UNIFIED] Bulk update environment variables 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>",
      "data": "<data>"
    },
    "name": "coolify_update_service_envs_bulk"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYes
siteYes
uuidYes
allow_compose_environment_overrideNo

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 destructive=true and readOnlyHint=false, so the overwrite risk is known from structured data. The description adds nothing beyond that: no statement on whether the bulk call replaces the entire env set or merges, no permission notes, and no effect of allow_compose_environment_override.

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?

A single short sentence with no padding, but it is under-specified rather than genuinely concise. The '[UNIFIED]' tag occupies space without adding meaning.

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?

A destructive bulk mutation with 4 undocumented parameters, no output schema and only safety annotations cannot be called correctly from this description. The agent has no idea of the payload element shape or override semantics.

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 coverage is 0% across 4 parameters and the description fills none of it. The shape of 'data' (array of items, element structure unspecified), 'site', 'uuid' and especially the risky 'allow_compose_environment_override' flag are all left undefined.

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?

Specific verb+resource: 'Bulk update environment variables for a Coolify service.' The word 'bulk' implicitly distinguishes it from the singular coolify_update_service_env sibling, though the sibling is never named. The '[UNIFIED]' prefix adds no information.

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 when-to-use guidance and no exclusions. Neither the singular sibling coolify_update_service_env nor the application-level bulk equivalent is referenced, so routing must be inferred from the word 'bulk' alone.

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