kde-desktop-mcp

Overview Schema Source Related Servers Discussions Admin

kde_session_use

Idempotent

Sets the persisted default private session for CLI clients that omit --session, while MCP desktop calls still require an explicit session.

Instructions

Set the persisted private default for CLI clients that omit --session. This does not change MCP desktop calls, which require an explicit 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_use"
  }
}

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

A4/5.0

Behavior4/5

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

Annotations already declare idempotent and non-destructive, so the description earns credit for adding that the setting is *persisted* (survives beyond this call) and that it only affects CLI default resolution, not MCP call routing. It omits where the value is stored or how to clear it, which is the main remaining gap.

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?

Two short sentences, no filler, and the primary effect is stated before the exclusion. Every sentence carries distinct information.

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 single-parameter tool with annotations covering the safety profile and no output schema, this is nearly complete. What remains unclear is the lifetime/reset semantics of the 'persisted' default and what 'private' implies in this context.

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_id parameter already carries a pattern, length constraints, and a description pointing to kde_session_create / kde_session_list. The description adds no additional meaning about the parameter, so the 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?

States a concrete verb ('Set') and resource ('the persisted private default') and scopes it to CLI clients that omit --session, which distinguishes it from sibling session tools that create/list/launch sessions. The phrase 'persisted private default' is slightly opaque jargon, keeping it short of a 5.

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

Usage Guidelines4/5

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

Gives a clear when: CLI clients omitting --session, and a clear when-not: MCP desktop calls, which require an explicit session. It does not name a sibling alternative, but the exclusions are stated explicitly rather than inferred.

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