Skip to main content
Glama

Check ffmpeg setup

check_setup
Read-only

Verify ffmpeg/ffprobe installation, confirm scene and blur detection filters exist, and identify the font used for timestamp labels before video processing.

Instructions

Confirm ffmpeg/ffprobe are installed, that scene and blur detection filters exist, and which font is used for timestamp labels.

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": "check_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

The readOnlyHint=true annotation already establishes this is a safe, non-mutating operation, and the description is consistent with that ("Confirm"). It adds useful specificity about exactly which conditions are verified, but says nothing about the shape of the result, whether a failure surfaces as an error or a reported status, or what the agent should do when a check fails.

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?

One sentence, front-loaded with the verb and the most important dependency (ffmpeg/ffprobe), then the secondary checks. No filler, no repetition of the title or annotation content.

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

Completeness3/5

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

For a zero-parameter diagnostic with no output schema, the description covers the inputs side perfectly but leaves the return contract unspecified: an agent cannot tell whether the response is a pass/fail boolean, a structured report per check, or an error on failure. Enumerating the checks partly compensates, but the result semantics remain a real gap for a tool whose entire value is its verdict.

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; baseline 4 applies. The description correctly does not invent inputs and instead spends its words on the checks performed.

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?

A specific verb ("Confirm") with three enumerated checks: ffmpeg/ffprobe installation, presence of scene and blur detection filters, and the font used for timestamp labels. This is unmistakably a diagnostics tool and cannot be confused with the sibling media-processing tools (detect_scenes, extract_frames, contact_sheet).

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is a preflight/diagnostic check to run before the media tools, since it validates ffmpeg and the filters that siblings depend on. There is no explicit statement of when to call it, when not to, or what to do with the result, so no alternatives or exclusions are named.

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