kde-desktop-mcp

Overview Schema Source Related Servers Discussions Admin

kde_session_show

Read-only

Inspect a managed private KWin session by ID to review its status and details, helping you verify an isolated desktop before controlling or managing it.

Instructions

Inspect a managed private KWin session by ID.

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_id": "<session_id>"
    },
    "name": "kde_session_show"
  }
}

Input Schema

Name	Required	Description	Default
`session_id`	Yes	Managed private session ID returned by kde_session_create or kde_session_list.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

B3.3/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 phrase "managed private" adds useful scoping context, but the description says nothing about behavior for an unknown or stopped session ID, or what inspection yields.

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?

One short sentence with the resource and the selector front-loaded; nothing extraneous and nothing buried.

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 read-only inspection tool with one fully documented parameter this is close to adequate, but with no output schema the agent has no idea what an "inspect" returns (state, geometry, status) or how failures surface. A brief note on the returned session information would close the gap.

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?

The single parameter has 100% schema description coverage, including the pattern and a pointer to kde_session_create/kde_session_list as the source of valid IDs. The description adds only the redundant "by ID" framing, so baseline 3 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?

The description pairs a specific verb ("Inspect") with a specific resource ("managed private KWin session") and a selector ("by ID"), which cleanly separates it from kde_session_list and kde_session_create. It stops short of naming a sibling, so it misses the top mark.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no explicit guidance on when to choose this over kde_session_list or kde_session_use. "By ID" implies the caller must already hold an ID, but the alternative-routing instruction lives in the schema's parameter text rather than the description.

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