kde-desktop-mcp

Overview Schema Source Related Servers Discussions Admin

kde_media_control

Destructive

Control playback on a selected MPRIS media player: play, pause, stop, skip tracks, or seek relative to the current position.

Instructions

Submit play, pause, play-pause, stop, next, previous, or a relative seek to one explicitly selected MPRIS player. For seek, seconds is required, must be non-zero, and is an offset (negative rewinds). Use kde_media_seek_to when you need an absolute playback position.

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>",
      "player": "<player>",
      "action": "<action>"
    },
    "name": "kde_media_control"
  }
}

Input Schema

Name	Required	Description
`action`	Yes
`player`	Yes
`seconds`	No
`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

A4/5.0

Behavior3/5

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

Annotations already declare openWorldHint and destructiveHint; the description adds useful seek semantics (non-zero, offset, negative rewinds) but never explains what makes the tool destructive (e.g. stop/next interrupting live playback) nor distinguishes stateful toggling of play-pause from play/pause. With annotations carrying the safety profile, this is adequate but leaves real behavioral gaps.

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 tight sentences, front-loaded with the action set before the seek caveat and the alternative. The action enumeration partly duplicates the schema enum, a minor redundancy, but nothing is padded.

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 destructive, open-world tool with no output schema and 25% schema coverage, the definition covers action and seek semantics but omits what a caller needs on failure modes (unknown player, no session), what happens to playback on stop, and how session selection interacts with the target player.

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 only 25% (session only), so the description must compensate — and it does for seconds: required for seek, must be non-zero, interpreted as a signed offset with negative rewinding. It adds nothing for player (beyond 'explicitly selected') and nothing for session, so it neither fully compensates nor matches schema-covered tools.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (submit a control action) and resource (one explicitly selected MPRIS player) and enumerates the action set, so it is immediately distinguishable from kde_media_seek_to and from inspection/listing siblings.

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?

Explicitly routes absolute-position needs to kde_media_seek_to, and the phrase 'one explicitly selected MPRIS player' implies the caller must pick a target first. It does not say when to prefer this over kde_media_inspect or kde_media_list, but the primary alternative is named with its condition.

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