Skip to main content
Glama
Sign In
computer-use

computer-use

by Cassius-stack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_apps

Read-only

Retrieves macOS applications, including currently running apps and installed /Applications bundles, with an option to return only running apps.

Instructions

List macOS applications (running apps and/or installed /Applications bundles).

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": "list_apps"
  }
}

Input Schema

NameRequiredDescriptionDefault
running_onlyNoIf true, return only currently running applications.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds value by stating that results span two distinct sources (running apps and installed /Applications bundles), which is effectively return-content information absent an output schema. It does not mention cost of scanning /Applications, possible permissions requirements, or result ordering.

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?

One sentence, front-loaded with the verb and resource, with the qualifying scope in a parenthetical. Nothing is wasted and nothing important is buried.

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

Completeness4/5

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

For a single-parameter read-only listing tool with full schema coverage and no output schema, this is nearly complete: it tells the agent what universe of items is returned. The only real gap is what the default result set looks like and whether one or both categories come back without the flag.

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% and the single parameter's own description fully explains the running_only filter. The description's 'running apps and/or installed bundles' phrasing confirms the default behavior of returning both, which is a small addition beyond the schema, but nothing more.

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 ('List') and a specific resource ('macOS applications'), then narrows scope to 'running apps and/or installed /Applications bundles'. That is clear enough to distinguish it from launch_app or list_windows by resource type, though it never explicitly names a sibling to contrast with.

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 when-to-use or when-not-to-use guidance, and no mention of alternatives such as list_windows or launch_app. The only hint at usage is the parenthetical scope, which tells the agent what the tool covers but not when to pick it.

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