Skip to main content
Glama
MCP Dokploy Online
by igoruam

schedule-one

Read-onlyIdempotent

Retrieve a single scheduled job by its ID from Dokploy to inspect its configuration and timing details.

Instructions

GET /schedule.one

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-one"
  }
}

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 already declare readOnlyHint, idempotentHint, and openWorldHint, and the description adds no behavioral context whatsoever — no note on what is returned, whether a missing schedule errors or returns empty, or any permission requirement. The "GET" token is redundant with readOnlyHint.

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?

It is short, but the brevity comes from under-specification rather than economy: a four-word endpoint string is not a front-loaded explanation of purpose.

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?

For a lookup tool requiring an identifier, an agent needs to know what it retrieves and how a missing or invalid ID behaves. With no output schema and 0% parameter coverage, the description leaves all of that unaddressed.

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?

Schema description coverage is 0% for the single required parameter scheduleId, and the description says nothing about it — no format, no source, no indication of where an agent obtains a valid ID. Only the property name itself carries meaning.

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.one" only restates the tool name as an HTTP route. The verb "GET" hints at a read and "one" weakly implies a single schedule, but the description never states what resource is fetched or how it differs from schedule-list or schedule-create.

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 any alternative such as schedule-list for enumerating schedules. The agent must infer everything from the name and sibling list.

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