kde-desktop-mcp

Overview Schema Source Related Servers Discussions Admin

kde_window_list

Read-only

Lists open windows in a managed private session or an explicitly selected real user desktop, enabling clients to inspect available windows before controlling them.

Instructions

List windows in a private session or explicitly selected user-desktop.

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": {
      "session": "<session>"
    },
    "name": "kde_window_list"
  }
}

Input Schema

Name	Required	Description	Default
`session`	Yes	Required target selector: a managed private session ID, or the exact value 'user-desktop' to explicitly opt into the real user desktop.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the useful constraint that reaching the real desktop requires explicitly opting in via 'user-desktop', but says nothing about result shape, window count, or ordering.

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 well-formed sentence with the scope front-loaded and zero filler. It is efficient, though it borders on under-specified for a tool with a strict selector parameter.

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 one-parameter read-only listing with full schema coverage and no output schema, the definition covers what an agent needs to invoke it correctly. A note on what a listed window entry contains would be nice but is not essential.

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 100% and the session parameter's pattern and description already explain the ID format and the 'user-desktop' literal. The description merely restates that scoping, adding no meaning beyond the schema, so the 3 baseline applies.

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 windows') plus the two scopes it operates in ('private session or explicitly selected user-desktop'). An agent can distinguish it from kde_window_find or kde_window_inspect without opening a schema, though the description never names those siblings explicitly.

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 the scoping clause: enumerate windows within a session. There is no explicit when-to-use/when-not guidance and no mention of when the more targeted kde_window_find or kde_window_inspect would be preferred over a full listing.

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