vlc-mcp

by jaseonline

Overview Schema Source Related Servers Discussions Admin

Python

Local

seek

Jump to a specific point in a VLC video or move forward/backward by time or percentage to navigate playback precisely.

Instructions

Seek to a specific position in the video. + or - seek relative to the current position and otherwise absolute.

Allowed values are of the form: [+ or -][:][:][] or [+ or -]% Examples: -10s -> seek 10 seconds backward +1h:2m:3s -> seek 1 hour, 2 minutes and 3 seconds forward 30s -> seek to the 30th second 50% -> seek to the middle -10% -> seek 10% back

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": {
      "value": "<value>"
    },
    "name": "seek"
  }
}

Input Schema

Name	Required	Description	Default
`value`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 12, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does disclose meaningful semantics beyond the input schema: the relative-vs-absolute mode switch and the supported unit combinations. What it omits is edge-case behavior — what happens when seeking past the end of the video, whether seeking works when nothing is loaded, and whether playback pauses or resumes after the seek.

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?

Front-loaded with the core semantic distinction, then the grammar, then examples — a sensible order for a format-heavy parameter. A few examples restate what the grammar already implies (e.g. '-10% -> seek 10% back'), but the redundancy buys clarity for a non-obvious syntax.

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 an output schema already covering return values, the definition covers the input contract thoroughly. The remaining gap is out-of-range and boundary behavior, which an agent would otherwise have to discover by trial.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% — 'value' has no description at all — so the description must compensate entirely, and it does: it supplies a formal grammar for the accepted string plus five concrete examples covering backward seconds, compound hours/minutes/seconds, absolute seconds, and percentage forward and backward. This is exactly the meaning the schema lacks.

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 and resource — 'Seek to a specific position in the video' — which is immediately distinguishable from siblings such as set_playback_rate or adjust_volume. An agent knows exactly what operation this performs without reading further.

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?

The description clearly establishes the choice between relative seeking ('+ or - seek relative to the current position') and absolute seeking ('otherwise absolute'), and the examples show which input form selects which mode. It stops short of naming alternatives (e.g. vlc_control) or stating when another tool would be preferable, so it is clear context without explicit routing.

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