Skip to main content
Glama
Sign In
computer-use

computer-use

by Cassius-stack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

batch_execute

Execute multiple macOS window, app, browser tab, and virtual cursor operations in one call, running steps in parallel by default.

Instructions

Execute multiple operations across ANY combination of macOS windows, window layouts, app launches, virtual cursors, and multiple browser tabs in ONE single click/call (parallel by default).

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": {
      "steps": "<steps>"
    },
    "name": "batch_execute"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepsYesHeterogeneous steps to execute. Each item specifies 'kind' ('window_action', 'get_window_state', 'manage_windows', 'launch_app', 'browser_open_tab', 'browser_tab_state', 'browser_tab_action', 'browser_manage', 'cursor_control') plus that tool's parameters.
parallelNoRun all steps concurrently via Promise.allSettled (default true). Set false for strict sequential order.
stop_on_errorNoWhen parallel=false, stop remaining steps if a step fails (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that execution is parallel by default, but the schema already states 'parallel=true' and describes Promise.allSettled; the description adds no information about result aggregation, failure semantics, ordering guarantees, permissions, or whether destructive actions like window or cursor changes are allowed.

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 definition is a single front-loaded sentence with no tangential detail. The phrasing 'ONE single click/call' is slightly redundant, but the sentence remains efficient and readable.

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

Completeness2/5

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

This is a complex heterogeneous batching tool with no annotations and no output schema. The description explains what it batches but omits critical behavior for an agent: what the response looks like, how step outcomes are reported, and how failures propagate in parallel versus sequential mode.

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 100%, and the schema explicitly lists the step 'kind' enum values and explains parallel and stop_on_error. The description adds the broad domain scope ('ANY combination') but no additional parameter semantics beyond the schema, so the baseline 3 is appropriate.

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

Purpose4/5

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

The description states a specific action ('Execute multiple operations') and enumerates the domains it can span: macOS windows, window layouts, app launches, virtual cursors, and browser tabs. It clearly distinguishes itself as a batch tool, though it does not explicitly name the individual sibling tools it replaces.

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

Usage Guidelines3/5

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

The phrase 'ANY combination' and 'ONE single click/call' implies this tool is for bundling heterogeneous operations, but there is no explicit when-to-use versus individual tools, no exclusions, and no guidance on when parallel batching is inappropriate.

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