Skip to main content
Glama

macos_list_apps

Lists running macOS apps with windows and returns their names, bundle IDs, and process IDs, marking the frontmost app so you can identify which app to focus.

Instructions

macOS only. List the running apps that have windows (name, bundle id, process id), marking the frontmost one and the host, the terminal or app this agent runs in, when macOS reports it. Use it to find the name or bundle id macos_focus_app takes. Needs no macOS permission.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it discloses several non-obvious behaviors: macOS-only applicability, that only apps with windows are listed, that the frontmost app is marked, that the agent's own host is flagged 'when macOS reports it' (a reliability caveat), and that no macOS permission is required. It does not state whether the call is read-only in effect or how ordering works, leaving a small gap.

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?

Three sentences, front-loaded with the platform constraint, with no filler. The parenthetical field list and the 'when macOS reports it' caveat both earn their place, though the phrase 'the host, the terminal or app this agent runs in' is slightly convoluted versus just saying 'marks the host app'.

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

Completeness5/5

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

There is no output schema and no annotations, yet the description supplies the return shape (name, bundle id, pid, frontmost marker, host marker), the environment constraint, and the permission posture. An agent has everything needed to call it and interpret the result correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero parameters and 100% schema coverage, there is nothing for the description to clarify at the parameter level; the baseline for a parameterless tool applies. The description instead spends its budget on return-value semantics, which is the right allocation here.

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

Purpose5/5

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

The description pairs a specific verb with a specific resource ('List the running apps that have windows') and enumerates the returned fields (name, bundle id, process id). It further disambiguates itself by naming the sibling it feeds (macos_focus_app), so an agent can separate it from the tab_* tools and the input tools without opening any schema.

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?

Explicit usage guidance: 'Use it to find the name or bundle id macos_focus_app takes' tells the agent exactly which downstream call this enables. No when-not/exclusion guidance is given (e.g. what to do if the target app has no windows), which keeps it below a 5.

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