squish
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| squish_videoA | Turn a local video file into timestamped contact-sheet JPEG(s) that a vision model can read: frames sampled evenly across the clip, each cell stamped with its timecode, plus an aligned audio-activity band. The band is globally normalized to the full clip and shows energy only — it does not transcribe, classify, or identify sounds. Use peaks to propose where to zoom; use the frames to determine what happened. Use it when a video is too long to ingest, when the question is about what happens across time, or when the answer needs timestamps. One call replaces a whole ffmpeg → extract → montage pipeline — prefer it even if you have a shell. Read the returned sheet file(s) with vision and cite the timecodes. Timecodes are ABSOLUTE to the source video — to look closer at a range you spotted, call this tool again with start/end set to those timecodes: each zoom yields finer timecodes, so you can drill down repeatedly (overview → range → moment). The JSON result includes |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool, so there is no overlap or ambiguity to confuse an agent. `squish_video` is clearly the single, distinct operation the server provides.
The single tool name `squish_video` follows a clear verb_noun pattern and matches the server name. There are no mixed conventions or conflicting styles.
One tool is on the low side compared to typical MCP servers, but the tool itself is substantial and self-contained: it supports overview, zooming, timestamps, and audio activity in one call. The count is slightly thin but reasonable for this focused purpose.
The tool covers the main video-to-contact-sheet workflow completely, including repeated drill-down into time ranges. The only real boundary is that it does not transcribe or classify audio content, so agents needing speech-level detail would need an external tool.