Skip to main content
Glama
Sign In
VLC MCP Server

VLC MCP Server

by QuantumNovice
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

vlc_set_volume

Set the VLC Media Player volume to a specific level from 0 (muted) to 512 (maximum).

Instructions

Set VLC volume. VLC accepts values from 0 (muted) to 512 (maximum).

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": {
      "volume": "<volume>"
    },
    "name": "vlc_set_volume"
  }
}

Input Schema

NameRequiredDescriptionDefault
volumeYesVLC volume from 0 to 512.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare that this is a non-read-only, non-destructive, non-idempotent operation, so the safety profile is covered. The description adds genuinely useful domain context by defining the 0-512 scale and noting that 0 means muted, but it says nothing about persistence, whether the change applies globally or per-session, or what happens if the value is out of range.

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 short sentences with the operational statement front-loaded and no filler. The second sentence largely duplicates the schema's range documentation, a small redundancy that keeps it below a perfect score.

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 tool with annotations present and no output schema, the definition covers what an agent needs to invoke it correctly. Only edge-case behavior, such as out-of-range rejection or scope of the volume change, is unaddressed, which is minor at this complexity.

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 100% and the single 'volume' parameter already carries a full description with minimum and maximum. The description restates the same 0-512 range, adding only the gloss that 0 equals muted and 512 equals maximum, which is marginal added meaning beyond the schema.

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 VLC volume'), which is unambiguous and cleanly separable from siblings like vlc_seek, vlc_pause, or vlc_get_status. It stops short of explicitly contrasting with any sibling, so it lands at clear-but-undifferentiated rather than a 5.

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 explicit when-to-use statement, no alternatives mentioned, and no prerequisites such as whether VLC must be running or whether this affects a specific player instance. Usage is only inferable from the tool name itself, which the description does not reinforce.

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