Skip to main content
Glama
Sign In
Linux Agent Desktop

Linux Agent Desktop

by aShanki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

desktop_open_task

Launches Qt, GTK, browser, or Wayland apps on a private display, keeping them isolated from user applications.

Instructions

Launch qt, gtk, browser, wayland-qt, wayland-gtk, or wayland-canvas on a private display. Never attaches to user apps.

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

Input Schema

NameRequiredDescriptionDefault
kindNoqt
scaleNo
outputsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden and does disclose an important trait: it runs on a private display and never attaches to user apps. However, it does not describe task lifecycle, cleanup expectations, resource impact, or whether the launched environment needs to be closed separately.

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?

The description is two short sentences and front-loads the launchable backends and the private-display constraint. Every sentence contributes useful information.

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 output schema means return values need not be explained, and the description covers the key isolation behavior. Still, for a tool with three undocumented parameters and no annotations, it leaves gaps around scale/outputs semantics and task lifecycle.

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

Parameters2/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 lists valid 'kind' values, which is useful, but it does not explain the 'scale' or 'outputs' parameters, their defaults, or how those values affect the private display.

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 a specific verb, 'Launch', and enumerates the display backends it can start, so the core purpose is clear. It also distinguishes the private-display behavior from attaching to user apps, though it does not explicitly name sibling tools for contrast.

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: launch one of the listed backends on a private display rather than attaching to existing user apps. There is no explicit guidance on when to choose this over sibling tools such as desktop_action or desktop_close_task, nor are prerequisites stated.

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