Skip to main content
Glama
MCP Dokploy Online
by igoruam

schedule-list

Read-onlyIdempotent

Lists scheduled tasks for a Dokploy resource by ID and type—application, compose stack, server, or Dokploy server—so you can review existing schedules.

Instructions

GET /schedule.list

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": {
      "id": "<id>",
      "scheduleType": "<scheduleType>"
    },
    "name": "schedule-list"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
scheduleTypeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered without the description. The description contributes nothing beyond that – no note on whether the list is paginated, filtered by the required id, or what it returns.

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?

Three words with no wasted prose, but this is under-specification rather than conciseness. The route string is not front-loaded around anything useful for an agent.

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 tool with two required, entirely undocumented parameters and no output schema needs the description to carry the burden. Nothing here explains the scoping semantics of the required id or the meaning of the enum, so an agent cannot call it correctly from the definition alone.

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 description coverage is 0% and both parameters are required. The description never explains what "id" identifies (a project? a server?) nor what the scheduleType enum values application/compose/server/dokploy-server mean, leaving an agent unable to construct a valid call confidently.

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?

"GET /schedule.list" only restates the tool name as a raw HTTP route. An agent can infer it reads a collection of schedules, but there is no plain-language verb+resource statement and nothing that distinguishes it from sibling schedule-one (single fetch) or the other list tools.

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 mention of when to prefer schedule-one, and no explanation of prerequisites. The only hint is the implicit HTTP GET verb embedded in the route string.

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