BCD — Bridge Control Delegate

schedule_workflow

Destructive

Run a saved workflow on a schedule, such as every weekday at 08:00, with no chat open. Review it first with get_workflow and pass the version it showed as expectedVersion: each run uses exactly that version and does not start if the workflow has changed. At each time BCD runs it on that computer the way run_workflow does, with the same permissions; the computer must be on and connected then. Inputs are kept by BCD's server, so never put secrets in them. Emails the account when a run fails or does not start (notify: failures, the default), after every run (always) or never. Returns scheduleId and the next run time. Requires read, write and process permissions.

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": {
      "workflowId": "<workflowId>",
      "expectedVersion": "<expectedVersion>",
      "time": "<time>",
      "timeZone": "<timeZone>"
    },
    "name": "schedule_workflow"
  }
}

Input Schema

Name	Required	Description
`days`	No	Days to run; omit for every day
`time`	Yes	Local time to run, HH:MM in 24-hour time
`inputs`	No	Values for the workflow's {{inputs}}, used at every run
`notify`	No	When to email the account: failures (default), always or never
`deviceId`	No	Computer name or id from list_devices. Optional with one computer online or a default set.
`timeZone`	Yes	The user's IANA time zone, such as America/Los_Angeles; ask the user if unsure
`workflowId`	Yes	A workflow saved with save_workflow on that computer
`expectedVersion`	Yes	The version get_workflow showed

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 9, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only give the safety envelope (readOnlyHint=false, destructiveHint=true, openWorldHint=true); the description goes well beyond by disclosing required permissions (read, write, process), the server-side retention of inputs with an explicit 'never put secrets in them' warning, the notification policy and its default, version-pinning/abort behavior, and shared permission inheritance with run_workflow.

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?

Dense single paragraph with the core action front-loaded and no filler sentences; each sentence carries distinct operational information (preconditions, secrets, notifications, return values, permissions). Slightly overloaded as one block rather than separated concerns, which costs it the top score.

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

Completeness5/5

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

For an 8-parameter mutation tool with nested objects and no output schema, the description covers returns ('scheduleId and the next run time'), permissions, failure/notification behavior, environment requirements, and the version-safety contract. Nothing an agent needs to invoke it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it explains the semantics of expectedVersion (each run uses exactly that version), the default of notify ('failures, the default'), and the server-side storage of inputs. It does not, however, add anything on time/timeZone formatting or deviceId resolution beyond the schema.

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?

Opens with a specific verb+resource+scope: 'Run a saved workflow on a schedule ... with no chat open', immediately distinguishing it from run_workflow (immediate execution), get_workflow (read) and list_scheduled_workflows (enumeration). An agent can select it without opening the schema.

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?

Explicitly prescribes the prerequisite sequence ('Review it first with get_workflow and pass the version it showed as expectedVersion') and names the sibling it parallels ('runs it on that computer the way run_workflow does, with the same permissions'). It also states the when-not condition: it 'does not start if the workflow has changed', and the environment precondition that the computer must be on and connected at that time.

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

All BCD — Bridge Control Delegate tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?