Skip to main content
Glama
Sign In
coolify-mcp

coolify-mcp

by frndchagas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Manage scheduled tasks

scheduledTasks

Create, list, update, delete, and view executions of cron jobs for applications and services. Automate recurring operations with scheduled tasks.

Instructions

Manage scheduled tasks (cron jobs) for an application or service. Actions: list, create (name, command, frequency), update, delete, list_executions (all but list/create need task_uuid).

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": {
      "resource": "<resource>",
      "uuid": "<uuid>",
      "action": "<action>"
    },
    "name": "scheduledTasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
uuidYesResource UUID
actionYes
commandNo
enabledNo
timeoutNo
resourceYes
containerNo
frequencyNoCron expression
task_uuidNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

B3.1/5.0
Behavior1/5

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

The annotation destructiveHint=false conflicts with the description listing 'delete' as an action, which implies a destructive operation. The description does not explain any other behavioral traits (e.g., side effects, permission requirements) and relies on the contradictory annotation. This is an annotation contradiction.

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

Conciseness5/5

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

The description is two sentences, front-loaded with the main purpose and then the action list. There is no filler or redundant information, making it concise and easy to scan.

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 10-parameter tool with five actions and no output schema, the description is too thin. It does not explain what each action returns, how resource/uuid are used, or the meaning of enabled/timeout/container. The contradiction with annotations further undermines the completeness of the behavioral context.

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

Parameters3/5

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

Schema description coverage is only 20%, so the description must compensate. It explains that create takes name, command, and frequency, and that all but list/create require task_uuid, adding meaning to key parameters. However, parameters like enabled, timeout, container, and resource remain undocumented in both the schema and the description, limiting compensation.

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 identifies the resource as 'scheduled tasks (cron jobs)' for application/service and enumerates the specific actions (list, create, update, delete, list_executions), giving clear operational scope. It distinguishes itself from sibling resource-management tools by focusing on scheduled tasks. The verb 'manage' is a bit broad, but the action list adds enough specificity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states the targeted resource types (application/service) and lists the available actions, providing clear context for when this tool applies. It also notes that all actions except list/create require task_uuid, which is a useful usage rule. However, it does not explicitly mention alternative tools or state when not to use it.

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