BCD — Bridge Control Delegate

run_command

Destructive

Run a shell command as the signed-in user and return its combined stdout/stderr, ending with [exit=N]. A command still running after 50 s keeps running as a process session until timeoutMs (default 120 s) and the reply gives its id for process_output and stop_process; for longer jobs use start_process. For commands that wait for input, use start_process. Reading, listing, searching and editing files also have their own tools with structured results: read_file, list_directory, search_files, search_content, edit_block and write_file; checking the computer, folder sizes and running programs have read-only ones: system_info, disk_usage and list_processes.

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": {
      "command": "<command>"
    },
    "name": "run_command"
  }
}

Input Schema

Name	Required	Description	Default
`cwd`	No
`command`	Yes
`deviceId`	No	Computer name or id from list_devices. Optional with one computer online or a default set.
`priority`	No	Scheduling priority. Use "low" for heavy or long-running work such as builds, training or test suites.	normal
`timeoutMs`	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.

Changed1 schema field changedOct 7, 2026
- changedInput schema / properties / timeoutMs / default
```
Previous value: -30000New value: +120000
```

Changed2 schema fields changedSep 30, 2026

removedInput schema / properties / cwd / default
```
Removed value: -"~"
```

addedInput schema / properties / workSessionId

Added value: +{
+  "description": "Work session from create_work_session. Pass the same ID on every call in this conversation; omit for legacy unscoped work.",
+  "format": "uuid",
+  "type": "string"
+}

First observedSep 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already flag readOnlyHint=false, destructiveHint=true and openWorldHint=true, but the description adds the operational specifics an agent needs: execution as the signed-in user, a 50 s threshold after which the command survives as a process session, the default timeoutMs of 120 s, and that the reply carries an id usable with process_output/stop_process.

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-loads the core behavior and exit-code format, then the fallback routing. Dense but every clause carries routing or behavioral information; only the long sibling enumeration at the end risks being skimmed.

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?

With no output schema, the description still explains the return value (combined stdout/stderr plus [exit=N]) and the async escape hatch. For a destructive, open-world command runner with only one required parameter, nothing essential is missing.

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 coverage is only 50%, so the description should carry more of the parameter burden. It explains the timeoutMs default and the process-session interaction, but says nothing about cwd, priority, deviceId or workSessionId, leaving those to the schema text. Partial compensation only.

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 (Run) and resource (shell command) with the exact return shape (combined stdout/stderr ending with [exit=N]). It distinguishes itself from siblings by naming start_process, read_file, list_directory, search_files, search_content, edit_block, write_file, system_info, disk_usage and list_processes as separate concerns.

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?

Explicit routing: use start_process for jobs longer than the timeout and for commands that wait for input; use the dedicated file tools for reading/listing/searching/editing; use the read-only system tools for machine inspection. This is when-to-use, when-not-to-use, and named alternatives in one paragraph.

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?