Skip to main content
Glama
dolphin-mcp-pilot

dolphin-mcp-pilot

ds_online_schedule

Activates an offline schedule so it begins triggering workflow runs. Use after creating a schedule and releasing its workflow online.

Instructions

Bring a schedule online so it starts triggering workflow runs.

Needed after ds_set_schedule, which creates schedules offline. The workflow itself must be online (ds_release_workflow). Reverse with ds_offline_schedule.

Args: project_name: Project name schedule_id: Schedule ID (from ds_set_schedule or ds_list_schedules)

Returns: {"schedule_id": int, "status": "ONLINE"}

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": {
      "project_name": "<project_name>",
      "schedule_id": "<schedule_id>"
    },
    "name": "ds_online_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
schedule_idYes
project_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the required prior state (schedule created offline, workflow released), the operational effect (runs begin triggering), and the reversing tool. It does not cover idempotency (what happens if the schedule is already online), failure modes, or permission requirements, which keeps it below a 5.

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

Conciseness4/5

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

The core instruction and prerequisites are front-loaded and the Args block is compact. The Args list largely duplicates names already visible in the schema, with only the schedule_id provenance earning its place, so it is efficient but not fully waste-free.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, but the description supplies the return shape ({"schedule_id": int, "status": "ONLINE"}), which covers that gap. However, for a state-changing operation with zero annotations, it leaves permission requirements and already-online/error behavior unaddressed.

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 0%, so the schema contributes nothing beyond names and types. The description adds provenance for schedule_id ('from ds_set_schedule or ds_list_schedules'), which is genuinely useful, but project_name is only restated as 'Project name' with no format or sourcing guidance.

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

Purpose5/5

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

States a specific verb ('Bring ... online') and resource (schedule) plus the concrete effect ('starts triggering workflow runs'), which lets an agent distinguish it from ds_set_schedule and ds_offline_schedule immediately.

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

Usage Guidelines5/5

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

Gives explicit ordering guidance ('Needed after ds_set_schedule'), a prerequisite ('The workflow itself must be online (ds_release_workflow)'), and names the inverse operation (ds_offline_schedule). This is exactly the when/when-not/alternative structure an agent needs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.