Skip to main content
Glama
Sign In
losslesscut-mcp

losslesscut-mcp

by bariswha
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Detect black frames

detect_black
Read-only

Detects black segments in a video, including fades, programme breaks, and ad breaks, to help identify cut points and gaps for editing.

Instructions

Finds black parts of the video, such as fades, breaks between programmes or ad breaks.

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": {
      "path": "<path>"
    },
    "name": "detect_black"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoEnd of the part to analyse (default: end of file)
pathYesAbsolute path of a file the user gave you
startNoStart of the part to analyse (default: start of file)
minDurationNo
pictureThresholdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful interpretation of what counts as a black part, but it does not disclose return format or how minDuration and pictureThreshold affect detection.

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?

A single front-loaded sentence with no filler. The purpose and examples are stated efficiently.

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 five-parameter detection tool with no output schema, the description is too thin. It omits what the detection returns and gives no explanation of the duration and picture threshold controls that materially affect results.

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

Parameters2/5

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

The description adds no parameter meaning beyond the schema. Schema coverage is 60%, with start/end documented but minDuration and pictureThreshold left without descriptions in either schema or prose, so the description does not compensate for the gap.

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?

States a specific verb and resource: 'Finds black parts of the video,' with concrete examples of fades and programme/ad breaks. It does not explicitly differentiate from siblings like detect_scenes or detect_silence, but the purpose is clear.

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?

The description gives no when-to-use guidance, no exclusions, and no comparison to alternative detection tools such as detect_scenes or detect_silence. Usage is only implied by the examples of black sections.

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