Skip to main content
Glama
MCP Dokploy Online
by igoruam

schedule-runManually

Idempotent

Triggers a Dokploy schedule to run immediately by its schedule ID, letting you execute a defined task on demand instead of waiting for its next planned run.

Instructions

POST /schedule.runManually

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": {
      "scheduleId": "<scheduleId>"
    },
    "name": "schedule-runManually"
  }
}

Input Schema

NameRequiredDescriptionDefault
scheduleIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

Annotations supply openWorldHint=true and idempotentHint=true, but the description adds no behavioral context of its own: no mention of side effects, permissions, execution timing, or whether retries are safe. Given the annotations already claim idempotency for what is nominally a manual trigger, some explanatory text was warranted and none is present.

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

Conciseness2/5

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

The text is a single line with no padding, so there is nothing to trim, but that is under-specification rather than conciseness. Nothing is front-loaded because nothing of substance is stated.

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?

This is an action/trigger tool with a required identifier, no output schema, and only two terse annotations. The description leaves the agent without enough information to invoke it confidently or predict its effect, so it is inadequate for the tool's complexity.

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?

The single required scheduleId parameter has 0% schema description coverage, and the description does not compensate at all - it never mentions the parameter or its accepted format. The field name is largely self-explanatory, which keeps this above the floor, but the description contributes no meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is only the HTTP route 'POST /schedule.runManually', which restates the tool name rather than explaining what the call does. It tells the agent nothing about what running a schedule manually means (immediate execution? queued job? side effects?) and does not distinguish it from siblings like schedule-update or volumeBackups-runManually.

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

Usage Guidelines1/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 prerequisites, and no mention of alternatives or when not to call it. An agent cannot tell from this line alone whether this triggers a job immediately or merely schedules one.

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