Cutible MCP Server

set_volume

Adjust a clip's audio level by specifying its ID and a volume value, solving the need to control sound intensity during video editing.

Instructions

Set clip volume.

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

Input Schema

Name	Required	Description	Default
`volume`	Yes
`clip_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 14, 2026

TDQS

C2.4/5.0

Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the basic action without any information about side effects, validation, error handling, or how the volume is applied. This is insufficient 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.

Conciseness4/5

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

The description is extremely concise, a single short sentence. It is free of unnecessary words and front-loaded with the core action. While it lacks depth, the brevity is appropriate for such a simple operation.

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

Completeness2/5

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

For a tool with no annotations, no output schema, and no parameter descriptions, the description is severely incomplete. It omits typical volume ranges, clip existence requirements, and any notes on how the volume affects the clip. An agent would lack essential context to use this correctly.

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

Parameters1/5

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

Schema description coverage is 0%, so the description must compensate by explaining the parameters. It does not mention what 'volume' represents (e.g., range, format, unit) or what 'clip_id' refers to. The description adds no value beyond the schema's bare property names.

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 'Set clip volume.' clearly states the action (set) and the resource (clip volume). It is not a tautology because it expands on the tool name by specifying 'clip' and 'volume'. However, it does not explicitly differentiate itself from sibling tools like set_speed, but the purpose 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 guidance on when to use this tool vs alternatives. It does not mention prerequisites, conditions, or comparisons to other tools. The description is too minimal to guide an agent on appropriate usage.

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