Framesleuth
Server 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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_videoA | Analyze any video and return the new report id. Works on any kind of video — a bug recording, a feature demo, a design walkthrough, a Loom, a phone capture — and distills it into a structured Context Bundle a coding agent can act on (fix a bug, add or change a feature, or build something new). Args:
path: Path to the video file (.mp4/.webm/.mkv/.mov/.avi).
repo_root: Repo to ground references against (pass the open workspace).
intent: The user's request to act on, e.g. "fix the save button that
hangs", "add a dark-mode toggle like the demo shows", or "build
this onboarding screen from the walkthrough". It is recorded on the
report and shapes the generated action prompt so the calling agent
does what the user actually asked.
skill: Built-in summary style — one of the names from Returns the report |
| list_skillsA | List built-in summary skills (names + descriptions) for |
| list_actionsA | List built-in action modes (names + descriptions) for |
| get_suggested_actionsA | Return the machine-readable next-step menu for a report. Each item is |
| renderB | Render a report as a shareable artifact.
|
| list_reportsA | List all available report ids (from any analyzed video). |
| get_reportA | Return the Context Bundle for a report id.
|
| get_repro_stepsA | Return the numbered reproduction steps for a report. |
| get_error_evidenceC | Return the timestamped error evidence for a report. |
| get_timelineC | Return the merged event timeline for a report. |
| get_keyframe_imageC | Return a keyframe image for a report by its index. |
| get_video_gifA | Render an animated GIF preview of the video for a report. Useful for embedding a short looping preview in an issue, chat, or PR
description. |
| locate_in_codeC | Return code candidates already grounded in the bundle, or re-ground now. |
| render_html_videoA | Render an HTML document (CSS / JS / canvas animation) to mp4/gif/webm. Use this to export a self-contained animated HTML page (e.g. one you just
designed) as a shareable clip. Captures the animation frame-by-frame
(full color, no dropped frames, no quality loss) and encodes a
color-correct H.264 MP4 / VP9 WebM / palette GIF — up to 4K, 5-60 fps.
Returns the absolute path to the encoded file, written under the bundle
directory. Requires the optional |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| fix_from_video | Emit a grounded action prompt — fix a bug, change a feature, or build new. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Each tool has a clearly distinct purpose: analyze_video is the entry point, get_* tools retrieve specific aspects of a report, list_* tools enumerate available options or reports, render tools produce output, and locate_in_code handles code grounding. No overlapping functionality.
All 14 tool names follow a consistent verb_noun pattern using snake_case (e.g., analyze_video, get_report, list_skills, render_html_video). No deviations or mixed conventions.
14 tools is well-scoped for a video analysis and rendering server. It covers analysis, report retrieval, listing, rendering, and code location without being overwhelming or sparse.
The tool surface is thorough for its domain: analyzing videos, retrieving all report components, rendering to multiple formats (Markdown, GitHub issue, test plan, GIF, MP4), and even grounding code locations. The only minor gap is the lack of a delete/update tool, but those are unnecessary for its core purpose.