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

linux-computer-use-mcp

by dhakseshr

open_application

Launch an installed Linux desktop app by name and receive a screenshot once its window appears and settles.

Instructions

Launch an installed desktop app by name, e.g. "Google Chrome", "Files", "Terminal". Returns a screenshot once the app's window has appeared and settled.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
screenshotNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose a key behavioral trait beyond the schema: the call blocks until the window 'has appeared and settled' and returns a screenshot. However it says nothing about failure behavior for a non-installed app, permission/auth requirements, or whether launching an already-running app refocuses or spawns a duplicate.

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?

Two sentences, front-loaded with the action and the resource, with zero filler. The examples are embedded inline rather than in a separate list, keeping it tight.

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 2-parameter launch tool with no output schema, the definition covers what it does, what it returns, and the timing semantics of the return. The remaining gap is the undocumented 'screenshot' toggle and error behavior, which keeps it from full marks.

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 compensate. It adds real meaning for 'name' by anchoring it to installed apps with human-readable examples, but the second parameter 'screenshot' (default true) is never mentioned, even though the description discusses returning a screenshot — leaving the agent unclear whether that return is controllable.

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: 'Launch an installed desktop app by name', and gives concrete name examples ("Google Chrome", "Files", "Terminal") that clarify what 'name' means. It does not explicitly differentiate itself from siblings like focus_window or list_applications, so it stops 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by 'installed desktop app' — the agent can infer the app must already exist — but there is no explicit when-to-use guidance, no pointer to list_applications for discovering valid names, and no mention of when to prefer focus_window for an already-running app.

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