kde-desktop-mcp

Overview Schema Source Related Servers Discussions Admin

kde_session_stop

Destructive

Stops a managed private KDE session and its tracked applications without affecting the live desktop. Use it to cleanly end a session identified by its session ID.

Instructions

Stop a managed private session and its tracked applications. Does not affect the live desktop. On shared servers, use only through the coordinator authorized to manage that 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_id": "<session_id>"
    },
    "name": "kde_session_stop"
  }
}

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

A3.8/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond them: the blast radius extends to tracked applications, the live desktop is untouched, and shared-server use requires an authorized coordinator. It does not explicitly say whether termination is graceful or immediate, or what happens to unsaved state.

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?

Three short clauses, front-loaded with the action, followed by blast-radius scoping and then the authorization constraint. Every sentence carries distinct information and there is no filler or redundancy.

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 destructive tool with annotations covering the safety hints and no output schema, the definition supplies the pieces an agent actually needs: scope of destruction, unaffected resources, and the authorization condition. It could be slightly more complete by stating irreversibility or the resulting session state.

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?

There is a single parameter with 100% schema description coverage, including the exact source of the ID (kde_session_create or kde_session_list) and a strict format pattern. The description adds nothing about the parameter beyond noting that 'its tracked applications' go with it, so the schema does the heavy lifting and the baseline of 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?

States a specific verb and resource ('Stop a managed private session and its tracked applications') and immediately scopes it against the desktop ('Does not affect the live desktop'), which separates it from desktop-wide operations. It stops short of naming a sibling or spelling out the create/list/show lifecycle relationship, so it is clear but not fully differentiated.

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 only guidance is a precondition: 'On shared servers, use only through the coordinator authorized to manage that session.' There is no statement of when to stop a session versus leaving it idle, no mention of dependent tools, and no exclusions relative to the sibling session tools. Usage is implied by the session lifecycle rather than explained.

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