Skip to main content
Glama

set_volume

Adjust Unflick media playback volume to a level from 0 to 100. Use it to control audio output directly from your MCP client.

Instructions

Set volume level

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": {
      "level": "<level>"
    },
    "name": "set_volume"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelYesVolume level (0-100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses nothing: not whether the change is absolute or relative, whether it clears a mute state, whether out-of-range values are clamped or rejected, or what the effect on existing settings is.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is four words with zero padding, but what remains reflects under-specification rather than disciplined conciseness. There is no front-loaded scope or constraint because there is essentially no content.

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?

For a simple one-parameter setter with full schema coverage and no output schema, the minimum needed to invoke it is present. However, the agent still cannot tell what the volume applies to or what happens on an out-of-range value.

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% for the single parameter, and the 0-100 range is already documented there, so the schema does the work. The description adds no meaning beyond it (e.g., whether 0 means mute or minimum audible), which is the baseline for a fully documented single parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Set volume level" restates the tool name set_volume almost verbatim and adds no distinguishing information. It does not say whether this controls the player's volume, system volume, or a specific audio stream, nor how it differs from siblings like audio_select or settings_set.

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 alternative named. The agent gets no signal about when this is the right call versus audio_select, equalizer_set, or settings_set.

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