VideoDB Director
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| doc_assistantC | Context for creating video applications using VideoDB |
| code_assistantB | Will give you data related to VideoDB SDK which allows developers to use videodb in python. IMPORTANT: Whenever user wants to write code related to videos, youtube videos or VideoDB specifically, always call this tool. |
| play_videoC | Play the video of the given stream link |
| call_directorC | The Director tool orchestrates specialized agents within the VideoDB server, efficiently handling multimedia and video-related queries. Clients should send queries that Director can interpret clearly, specifying tasks in natural language. Director will then delegate these queries to appropriate agents for optimized results, utilizing defaults and contextual information if explicit parameters are not provided. Director handles queries such as:
Clients should provide queries clearly aligned with Director's capabilities, allowing Director to use contextual defaults when explicit parameters like IDs or collection details are not specified. IMPORTANT: if you have a previous response of this method with an appropriate session_id, please provide that session_id in the next request to continue the conversation.
IMPORTANT: It is MANDATORY to send the |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| doc_assistant | Context for creating video applications using VideoDB |
| code_assistant | Context for creating video applications using VideoDB |
TDQS
Scored across 4 tools
The tools are highly ambiguous and overlapping. The 'call_director' tool appears to be a monolithic interface that handles nearly all functionality described (uploading, indexing, summarization, dubbing, video creation, audio generation, video editing, streaming, transcription, pricing, meeting analysis, etc.), making it unclear when to use the other tools. 'code_assistant' and 'doc_assistant' might overlap in providing development support, and 'play_video' could be seen as a subset of 'call_director's streaming capability. This creates significant confusion for tool selection.
Naming is inconsistent with mixed conventions. 'call_director' uses a verb_noun pattern, 'code_assistant' and 'doc_assistant' use noun_noun patterns, and 'play_video' uses verb_noun. While readable, the lack of a uniform pattern (e.g., all verb_noun like 'call_director', 'assist_code', 'assist_docs', 'play_video') reduces predictability. The styles vary without a clear rationale, though they are not chaotic.
The tool count of 4 is too few for the broad scope implied by the 'call_director' description, which covers over 20 distinct capabilities (e.g., uploading, indexing, dubbing, video generation). This forces a single tool to handle too many diverse operations, making the surface feel thin and under-scoped. A more appropriate set would break these into multiple specialized tools for better coherence.
The tool set is severely incomplete relative to the domain described. While 'call_director' lists many video-related operations, the other tools ('code_assistant', 'doc_assistant', 'play_video') do not provide complementary CRUD or lifecycle coverage. For example, there are no dedicated tools for core actions like 'upload_video', 'search_videos', or 'transcribe_video', leaving agents to rely on a single monolithic tool that may not handle all scenarios effectively, leading to potential dead ends.