Skip to main content
Glama
linux-computer-use-mcp

linux-computer-use-mcp

by dhakseshr

list_applications

Lists installed desktop applications on a Linux desktop, with optional substring filtering to identify apps available for viewing or control.

Instructions

List installed desktop applications (optionally filtered by a substring).

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_applications"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. "List" implies a non-destructive read, but the description does not confirm read-only semantics, say whether the enumeration is cached or queried live, or indicate rough cost for machines with many installed apps. For a simple read operation the gap is modest rather than severe.

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 sentence with zero filler. A parenthetical for the optional parameter is reasonable structure, though splitting the filter behavior into its own clause would read marginally cleaner.

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?

The tool is simple and an output schema exists, so return values need not be explained. Still, the definition omits whether it reports running versus merely installed applications, which is the main ambiguity for an agent deciding between this and its window/application siblings.

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 0% and the single parameter ("filter") has no schema description, so the description must compensate. Saying it is a substring filter adds real meaning beyond the bare schema, but leaves open case sensitivity, whether it matches display names only, and that an empty string returns everything.

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?

States a specific verb and resource ("List installed desktop applications") that an agent can immediately recognize. It does not explicitly distinguish itself from near neighbors like list_windows or open_application, leaving the agent to infer that this enumerates installed programs rather than open windows.

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?

The phrase "optionally filtered by a substring" implies the intended usage pattern (enumerate, optionally narrow), but there is no explicit when-to-use guidance, no mention of when not to use it, and no routing to alternatives such as list_windows for currently open windows.

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