BCD — Bridge Control Delegate

save_workflow

Destructive

Save 1–20 ordered steps on this computer, to rerun later with run_workflow; saving runs nothing. Each step is one call to a tool listed here (read_file, read_multiple_files, list_directory, search_files, search_content, stat_path, write_file, edit_block, make_directory, move_path, copy_path, write_pdf, edit_spreadsheet, edit_docx, run_command) with that tool's own arguments, so a run does only what those calls do on their own. Use {{inputName}} in file arguments to supply new values later; commands must be fixed text. Definitions and inputs are stored locally, not in the relay: do not put secrets in them. Saving sets no schedule; schedule_workflow, where listed, runs a saved workflow on one. With an existing workflowId it replaces that definition (only this caller’s), and the earlier steps are not kept.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes
`steps`	Yes
`deviceId`	No	Computer name or id from list_devices. Optional with one computer online or a default set.
`workflowId`	No
`description`	No
`workSessionId`	No	Work session from create_work_session. Pass the same ID on every call in this conversation; omit for legacy unscoped work.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 8, 2026

addedInput schema / properties / steps / items / properties / arguments / description

Added value: +"The arguments of that tool, as its own input schema takes them (no workSessionId)"

addedInput schema / properties / steps / items / properties / tool / description
```
Added value: +"The tool this step calls"
```

addedInput schema / properties / steps / items / properties / tool / enum

Added value: +[
+  "read_file",
+  "read_multiple_files",
+  "list_directory",
+  "search_files",
+  "search_content",
+  "stat_path",
+  "write_file",
+  "edit_block",
+  "make_directory",
+  "move_path",
+  "copy_path",
+  "write_pdf",
+  "edit_spreadsheet",
+  "edit_docx",
+  "run_command"
+]

removedInput schema / properties / steps / items / properties / tool / maxLength
```
Removed value: -96
```
removedInput schema / properties / steps / items / properties / tool / minLength
```
Removed value: -1
```

AddedSep 30, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the destructiveHint annotation, it discloses that saving executes nothing, that definitions/inputs are stored locally rather than in the relay, that secrets must not be included, and that supplying workflowId replaces the caller's earlier definition without keeping prior steps. This is exactly the extra behavioral context annotations cannot convey.

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?

Front-loaded with the core purpose and then layers constraints efficiently; every sentence adds information (templating, local storage, scheduling, replacement). Dense but not padded, though the long parenthetical tool list makes it heavier than strictly necessary.

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

Completeness4/5

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

For a 6-param tool with no output schema and partial schema coverage, the description is thorough on inputs, storage, security, and replacement behavior. It does not indicate what the call returns (e.g., a workflowId for later use), which is the one notable gap.

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 only 33%, so the description carries meaningful load: it explains the steps structure (one call to a listed tool with that tool's own arguments), the {{inputName}} templating for later value substitution, fixed-text command constraints, and the replace-on-workflowId semantics. Only name/description params remain undocumented, but they are self-evident.

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 (Save) and resource (ordered workflow steps on this computer), and immediately distinguishes itself from run_workflow and schedule_workflow. An agent can identify this as the definition-storing tool without opening any 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 frames the use case ('to rerun later with run_workflow') and rules out the common confusions: 'saving runs nothing' and 'saving sets no schedule; schedule_workflow... runs a saved workflow on one.' It names the alternative and the condition that selects it.

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

Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?