Skip to main content
Glama

desktop_batch

Runs a bounded, sequential JSON command batch for desktop automation, with a wall-clock timeout and optional stop-on-error handling.

Instructions

agent-desktop batch: Execute a bounded, sequential, non-atomic JSON command batch

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": {
      "commands_json": "<commands_json>"
    },
    "name": "desktop_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeout_msNoAbsolute wall-clock budget for the whole non-atomic batch
commands_jsonYesJSON array of {command, args} objects
stop_on_errorNoHalt the batch on the first failed command

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose key traits: execution is sequential (order matters), bounded by a timeout, and non-atomic (partial failures leave partial state changes). However, it does not say which commands are valid, what happens to already-applied commands on failure, or what the response looks like per command.

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

Conciseness5/5

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

A single dense clause with zero filler; every modifier (bounded, sequential, non-atomic, JSON) carries information. The critical qualifier 'non-atomic' is not buried.

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 orchestration tool with no annotations and no output schema, yet the description omits the command vocabulary, per-command result/error reporting, and whether a desktop session must be active. For a tool that can mutate system state in bulk, that leaves too much unspecified.

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 100%, so all three parameters are already documented with types and defaults. The description adds only loose framing ('bounded' relating to timeout_ms, 'non-atomic' relating to stop_on_error) without explaining the interaction between stop_on_error and the atomicity caveat.

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?

States a specific verb+resource combination ('Execute a ... JSON command batch') and qualifies it with three meaningful modifiers (bounded, sequential, non-atomic). This clearly distinguishes it from the single-action desktop_* siblings, though no sibling is named explicitly.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to choose a batch over issuing individual desktop_* calls, nor any exclusion criteria. An agent must infer that batching is preferable for multi-step sequences, which is reasonable but not stated.

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