Skip to main content
Glama
Sign In
vlc-mcp

vlc-mcp

by jaseonline
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_aspect_ratio

Adjust the VLC video aspect ratio to fix stretched or letterboxed playback by selecting a preset ratio or resetting to default.

Instructions

Set the video aspect ratio.

Args: ratio: One of 1:1, 4:3, 5:4, 16:9, 16:10, 221:100, 235:100, 239:100, or "default" to reset.

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": {
      "ratio": "<ratio>"
    },
    "name": "set_aspect_ratio"
  }
}

Input Schema

NameRequiredDescriptionDefault
ratioYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses that the change is reversible via the 'default' reset value, but nothing about whether the ratio applies immediately to current playback, persists across items, or requires an active video. That is a significant gap for a mutation tool.

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?

Purpose is front-loaded in one line, followed by a compact Args block that carries only the value list. No filler sentences and nothing redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple, one required parameter, and an output schema exists so return values need no explanation. Combined with the enumerated value list, it is largely adequate, but the absence of any statement about when the change takes effect leaves an operational gap.

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% and the schema only declares a bare string named 'Ratio', so the description is the sole source of meaning: it enumerates the eight accepted ratio values plus 'default' for reset. It loses a point only for not clarifying case sensitivity or format tolerance (e.g., '16:9' vs. '1.778').

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 opens with a specific verb+resource: 'Set the video aspect ratio,' which is unambiguous and distinguishable from sibling setters like set_playback_rate or set_volume. It never explicitly contrasts itself with an alternative, but the purpose is readable without opening the schema.

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 (e.g., must a video be playing?), and no mention of alternatives. The only hint of context is that 'default' resets the ratio, which is a value semantic rather than usage guidance.

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