Skip to main content
Glama

Check Reels setup

reels_doctor
Read-onlyIdempotent

Check dependencies for Reels Research MCP: yt-dlp, ffmpeg, anonymous Reel access, video streaming, and Parakeet Redux speech-to-text. Run after setup or when reels_fetch fails.

Instructions

Check everything this server needs on this machine, with timings: yt-dlp, ffmpeg, anonymous Reel access, the video stream, and local speech-to-text (Parakeet Redux). Run it after installing or when reels_fetch fails.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "reels_doctor"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's contribution is the diagnostic detail: it probes local binaries, anonymous network access, the video stream, and a local STT model, and reports timings. It does not say how failures are surfaced or what the report looks like, but for a read-only check that is a minor gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler. The scope enumeration is front-loaded and the usage trigger is packed into the second sentence, so both payloads land before an agent stops reading.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-param, read-only diagnostic with no output schema, the description covers what is checked, when to run it, and the failure path. Only the interpretation of results (pass/fail shape) is unspecified, which is acceptable given the low complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter meaning to convey and the baseline of 4 applies. The description correctly signals a no-argument, run-and-see invocation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Check') plus the exact scope: yt-dlp, ffmpeg, anonymous Reel access, the video stream, and Parakeet Redux speech-to-text. That enumeration makes it unmistakably a dependency-diagnostic tool and clearly distinct from reels_fetch and reels_links.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit trigger conditions: 'Run it after installing or when reels_fetch fails.' The failure-recovery routing names a sibling and the condition that selects this tool, leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools