Skip to main content
Glama

desktop_list_apps

Lists running GUI applications and optionally filters by app name, so you can identify open windows before inspecting or automating them.

Instructions

agent-desktop list-apps: List all running GUI applications (--app to filter)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "desktop_list_apps"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNoFilter to application by name
timeout_msNoInventory deadline in milliseconds (default 5000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden and adds almost nothing: it doesn't say the operation is read-only, whether OS accessibility/automation permissions are required, what happens when the inventory deadline expires, or what the result looks like. Only the existence of a name filter is conveyed.

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?

A single, front-loaded line with the resource scoping stated first and the filter hint second. Minor waste in the redundant 'agent-desktop list-apps:' prefix that duplicates the tool name.

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?

For a tool with zero annotations and no output schema, the description should tell the agent what a call returns (app names? PIDs? bundle IDs?) and any permission prerequisites; it does neither. It is technically callable from the schema alone, but the agent cannot anticipate results or failure modes.

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%, so both parameters (app, timeout_ms) are already documented, giving a baseline of 3. The description's '--app to filter' merely restates the app parameter using a CLI flag name and says nothing about timeout behavior beyond what the schema provides.

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 gives a specific verb and resource — 'List all running GUI applications' — which an agent can distinguish from window- or display-oriented siblings. It stops short of explicitly contrasting itself with desktop_list_windows, but the resource is concrete enough to route correctly.

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?

Usage is only implied: the agent infers 'call this when you need the set of running apps.' There is no statement of when to prefer it over desktop_list_windows or desktop_find, and no preconditions or exclusions are mentioned.

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