Skip to main content
Glama
kde-desktop-mcp

kde-desktop-mcp

by marvin1099

kde_media_inspect

Read-only

Read playback status, title, artist, album, position, and duration from an explicitly selected MPRIS player in a specified desktop session.

Instructions

Read playback status, title/artist/album, current position, and duration from one explicitly selected MPRIS player.

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>"
    },
    "name": "kde_media_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
playerYes
sessionYesRequired 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.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered structurally. The description adds real value by enumerating the fields read back (status, metadata, position, duration), but says nothing about failure modes such as a missing/stale player name or a player that is not playing, which is the remaining useful behavioral detail.

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?

A single front-loaded sentence that names the verb, the returned fields, and the scoping constraint with no filler or redundancy. Every clause carries 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?

With no output schema in play, the description takes on the return-value burden and does so by enumerating the fields returned. The one substantive gap is how to specify the `player` identifier, which is the only piece an agent could get wrong when invoking this simple two-parameter read tool.

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 50%: `session` is well documented in the schema, while `player` has only length constraints. The description partially compensates by clarifying that `player` names a single MPRIS player, but it never states the expected identifier form (bus name vs. friendly name) or where to obtain it, so the agent still cannot construct that argument from the description alone.

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?

"Read playback status, title/artist/album, current position, and duration" gives a specific verb and enumerates the exact resource being fetched, and "from one explicitly selected MPRIS player" scopes it to a single target. It implicitly separates itself from list/control siblings (it reads rather than enumerates or mutates), but no sibling is named, so the differentiation is inferred rather than stated.

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 phrase "one explicitly selected MPRIS player" implies the caller must already know which player to target, which hints that a listing step (e.g., kde_media_list) precedes this call. However, there is no explicit when-to-use/when-not guidance and no comparison to the media_control or media_seek_to siblings, leaving the agent to infer the workflow.

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