Skip to main content
Glama
kde-desktop-mcp

kde-desktop-mcp

by marvin1099

kde_media_seek_to

Destructive

Seek a specified MPRIS media player to an absolute playback position from 0 to 86400 seconds, then inspect the player because the request is not verified.

Instructions

Seek one exact listed MPRIS player to an absolute position from 0 through 86400 seconds. The request is not verified; inspect the player afterward.

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

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.
position_secondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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, but the description adds genuinely new behavioral context: the request is not verified, so the agent knows the call is fire-and-forget and must confirm the result itself. That is exactly the kind of caveat annotations cannot express. It stops short of saying what happens to playback state or whether other players are untouched.

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 and scope, with the caveat second. Slight redundancy in restating the numeric range already enforced by the schema, but no wasted prose.

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 three-parameter destructive tool with no output schema, the description covers the essentials: target selection, absolute positioning, and the need for post-hoc verification. A note on whether seeking interrupts playback or affects only the named player would close the remaining gap.

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 description coverage is only 33% – only 'session' is documented – so the description has to carry the other two parameters. It does add meaning for 'player' (must be an exact value from a listing) and for 'position_seconds' (absolute, not a relative offset), but the 0–86400 bound merely repeats the schema's minimum/maximum and no format or unit nuance is added beyond 'seconds'.

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: seek a listed MPRIS player to an absolute position in seconds. The word 'listed' implicitly ties it to the media listing tool and 'absolute position' separates it from relative-step controls. It is clear but does not explicitly name the sibling it differs from, e.g. kde_media_control.

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?

'Seek one exact listed MPRIS player' implies the player identifier must come from a prior listing call, and 'inspect the player afterward' routes the agent to the inspect tool. There is no explicit when-not guidance or statement of how this differs from kde_media_control, so usage is only implied.

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