Skip to main content
Glama

act

Run ordered UI steps on a macOS app window in the background without taking focus, moving the pointer, or changing the clipboard. Stops at first failure and returns what changed.

Instructions

Run steps on an app's window in the background, without touching the user's focus, pointer or clipboard. Steps run in order, each waits until the app has finished reacting, and the batch stops at the first failure. Returns what changed. Put several steps in one call. Steps: click REF|X,Y · double REF · right REF · set REF VALUE · type [REF] TEXT · key COMBO [xN] · menu A > B · pick REF OPTION · select REF · focus REF · scroll REF up|down|left|right [N] · show REF · drag REF|X,Y to REF|X,Y (to a ref: takes its place) · wait gone REF|REF|text "T"|500ms [within 10s] · lane (move the app's windows off screen, where they still render and take clicks)

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

Input Schema

NameRequiredDescriptionDefault
appYes
stepsYes
windowNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden and discloses important traits: background execution, ordered steps, waiting until the app reacts, stopping at the first failure, and returning what changed. It does not mention permission requirements, reversibility, or the potentially destructive nature of click/type/key actions, so it is strong but not complete.

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?

The description is front-loaded with purpose and behavioral rules, then compactly lists the step grammar. The step list is dense but every token is necessary to specify valid inputs, and there is no wasted explanatory prose.

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

Completeness3/5

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

For a complex automation tool with no annotations, no output schema, and 0% schema description coverage, the description covers step syntax and key execution behavior well. However, it does not define the app identifier format, optional window semantics, permission expectations, or the shape of the returned changes, leaving meaningful gaps for correct invocation.

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 0%, so the description must compensate. It does so extensively for the steps parameter by spelling out the step grammar, but it leaves the app and optional window parameters undefined in format or behavior. This is useful partial compensation rather than full parameter semantics.

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 verb and resource: running steps on an app's window in the background. It also clarifies the non-intrusive scope by saying it avoids the user's focus, pointer, and clipboard. It does not explicitly distinguish itself from siblings such as observe, see, script, or record, so it stops short of a 5.

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

Usage Guidelines4/5

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

The description gives clear usage context for background multi-step app interaction and explicitly advises batching steps: 'Put several steps in one call.' It does not state when to use this instead of alternatives or any when-not conditions, which keeps it below 5.

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