Skip to main content
Glama

Related Servers

Alternatives to vidlens-mcp

No user-submitted related servers found.

    Related Servers

    TDQS

    A3.8/5.0

    Scored across 18 tools

    Disambiguation4/5

    Descriptions actively steer the agent away from the wrong tool (e.g. video_subs before ASR, video_sheet/frames instead of video_full, video_window for a single span vs video_watch for incremental progress), which is unusually strong guidance. Still, there are clusters of near-neighbours: video_brief / video_watch / video_window all can yield transcripts of the same footage, and video_sheet / video_frames / video_visual_scan / video_ocr all sample frames, so a hurried agent could easily pick the wrong one.

    Naming Consistency4/5

    Nearly everything follows a single `video_<noun>` scheme with short, readable suffixes. The two infrastructure tools break the prefix (vidlens_models, vidlens_doctor), and a few names mix styles (video_job_start is noun_verb, video_full is an adjective), but the overall set is predictable.

    Tool Count4/5

    18 tools is on the heavy side, but they form a deliberate cost tier (meta → plan → window → sheet → OCR → job) rather than a flat pile. Each tool has a stated cheaper alternative it exists to replace, though a few of the visual/transcript tools could plausibly be merged.

    Completeness5/5

    The surface covers the full video-analysis lifecycle: metadata, subtitles, planning, incremental watching, time windows, audio events, soundscape, frame/sheet/scan visuals, OCR, comments, plus model management, diagnostics and async job polling for long runs. No obvious dead ends remain for the stated domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues