kde-desktop-mcp

Overview Schema Source Related Servers Discussions Admin

kde_display_list

Read-only

Lists logical display geometry for a selected KDE session, helping you inspect screen layout and dimensions before automating desktop tasks.

Instructions

List logical display geometry in the selected target session.

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_display_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.6/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 by structured data. The description adds that results are scoped to a selected target session, which is useful context, but says nothing about ordering, counts, or what geometry values come back.

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?

A single front-loaded sentence with a specific verb and resource and no filler. Nothing in it could be cut without losing meaning.

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 one-parameter read-only list tool this is close to adequate, and the schema carries the parameter burden. However, with no output schema present, the description does not hint at what the returned geometry entries contain, which is the main remaining gap.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already spells out the session selector, including the 'user-desktop' opt-in and the agent-session pattern. The description reinforces the session scoping but adds no new syntax, so it neither helps nor hurts beyond the strong schema.

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 logical display geometry') scoped to a target session, so an agent knows it enumerates display/headless geometry rather than windows or media. It does not explicitly differentiate itself from sibling list tools (kde_window_list, kde_session_list), leaving that distinction to the resource noun alone.

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 'in the selected target session' implies this is the read-side companion to session selection, but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent must infer that a session must be established first.

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