framedeck
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| framedeck_extractA | Download a video (TikTok, Instagram, YouTube, X, or a local file path) and extract the handful of visually distinct frames, skipping near-duplicates. Returns a manifest with an absolute file path per frame — read those paths as images to actually see the video. Use this whenever you are asked about the contents, design, or UI of a video. |
| framedeck_infoA | Fetch a video's metadata — caption, author, duration — without downloading it. Cheap first call when the caption alone may answer the question. |
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 2 tools
framedeck_extract and framedeck_info are cleanly separated: one downloads video content and returns visual frames, while the other fetches metadata without downloading. There is no realistic overlap in what they are used for.
Both tools share the clear framedeck_ prefix and snake_case convention. The only minor inconsistency is that 'extract' is a verb while 'info' is a noun, so the action pattern is not perfectly uniform.
Two tools is slightly below the typical 3-15 range, but it fits the server's narrow purpose: obtaining video metadata and extracting representative frames. Each tool earns its place, so the count feels reasonable rather than thin.
For the apparent domain of video understanding, the surface is complete: framedeck_info covers quick metadata lookups and framedeck_extract covers the visual content workflow. There is no obvious missing operation or dead end.