kde-desktop-mcp

Overview Schema Source Related Servers Discussions Admin

kde_window_set_minimized

DestructiveIdempotent

Minimize or restore a KDE window by setting its minimized state explicitly and verifying the result; use false to restore.

Instructions

Set a window's minimized state explicitly and verify it. Setting false restores it; live changes may change user focus.

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>",
      "window_id": "<window_id>",
      "minimized": "<minimized>"
    },
    "name": "kde_window_set_minimized"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations declare destructiveHint=true and idempotentHint=true, and the description adds the concrete reason for the destructive flag: live changes may alter user focus. It also notes that state is verified after the set, which is useful post-call context, though it doesn't explain how verification surfaces (no output schema).

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?

Two compact sentences, with the primary action front-loaded and the restore/focus caveats following. 'and verify it' is slightly vague but the overall structure is efficient and earns its words.

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 simple three-parameter mutation with no output schema, the description covers the action, the polarity, the side effect on focus, and the post-set verification. Only window_id semantics and error behavior are left unaddressed, which is minor here.

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 only 33% – only 'session' is documented – so the description must compensate. It does explain the semantics of the 'minimized' boolean (false restores the window), but leaves window_id meaning to inference, so compensation is partial.

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: 'Set a window's minimized state explicitly', with the boolean polarity explained. It is clearly distinguishable from siblings like kde_window_activate or kde_window_set_geometry, though it doesn't name any alternative for contrast.

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?

Implies usage through 'Setting false restores it', which tells the agent when the false value applies, but it never states when to prefer this tool over kde_window_activate or other window tools, nor any prerequisites.

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