Skip to main content
Glama

screen_list_apps

Read-only

Windows and macOS: the apps open on the user's computer (hwnd, title, app, whether in front), to pick one for screen_open_app. If the app you need isn't there, ask the user to open it. On a Mac, shortcuts use Meta (Command): Meta+C copies.

response_detail (summary|ids|compact|full), fields (dotted paths), cursor (next page) — see the server instructions.

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

Input Schema

NameRequiredDescriptionDefault
cursorNo
fieldsNo
response_detailNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine value beyond that — platform support, the shape of each returned entry, and pagination via cursor. However, the closing note about Mac Meta/Command shortcuts (Meta+C copies) is unrelated to listing apps and muddies rather than clarifies behavior.

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

Conciseness2/5

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

The opening sentences are well front-loaded, but the Mac shortcut aside ('Meta+C copies') is off-topic for a listing tool and occupies a full sentence that earns no place. The parameter block is a compressed fragment that reads like a schema stub rather than 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 three-parameter, no-output-schema read tool, it covers the essentials: what comes back per entry, platform limits, pagination, and the fallback when an app is missing. The dangling shortcut note and the hand-off of parameter behavior to server instructions leave the definition partly incomplete for an agent that only sees this text.

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 carry all three parameters — and it does name them: response_detail with its value set (summary|ids|compact|full), fields as dotted paths, and cursor as next page. That is meaningful semantics the bare schema lacks, but it defers the actual rules to 'see the server instructions', leaving format and interaction between response_detail and fields unexplained.

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 the resource clearly — the apps open on the user's computer — and enumerates the returned attributes (hwnd, title, app, whether in front), plus platform scope (Windows and macOS). It differentiates itself from siblings by naming screen_open_app as the consumer. The verb is implicit ('the apps open') rather than an explicit 'List', which keeps it just 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?

It gives the downstream purpose ('to pick one for screen_open_app') and a concrete fallback: if the needed app is absent, ask the user to open it. That is real when-to-use guidance tied to a named sibling. It stops short of 5 because it never states when not to call it (e.g. use screen_look/screen_status instead).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.