Skip to main content
Glama
Sign In
vlc-mcp

vlc-mcp

by jaseonline
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_playback_rate

Adjust VLC playback speed by setting a rate above 0, where 1.0 is normal, 2.0 is double, and 0.5 is half speed.

Instructions

Set the playback speed. 1.0 is normal speed, 2.0 is double, 0.5 is half. Must be greater than 0.

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": {
      "rate": "<rate>"
    },
    "name": "set_playback_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It usefully defines the unit scale (1.0 normal, 2.0 double, 0.5 half) and a validity constraint (must be greater than 0), but says nothing about whether the change applies to current playback only, persists across items, affects audio pitch, or what the response contains.

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?

Three short sentences, front-loaded with the purpose and followed by the value semantics and the constraint. Nothing is redundant, though the constraint sentence could be merged for tighter flow.

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 one-parameter setter with an output schema available, the description covers purpose, value scale, and validity. The main remaining gap is scope of effect (current item vs. global), which matters for a playback control tool.

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 0%, so the description must compensate, and it largely does: it explains the meaning of the single `rate` value with concrete reference points and a lower-bound constraint. It stops short of stating an upper bound or precision expectations.

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?

The description names a specific verb and resource ("Set the playback speed") that is clearly distinct from siblings like set_volume, set_aspect_ratio, or seek. It does not explicitly say how it differs from those siblings, but the resource itself is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives or edge cases (e.g., whether it applies to the currently playing item only or persists). Usage is only implied by the tool name and purpose sentence.

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

Deploy Server

Other Tools