Skip to main content
Glama

videogenie_capabilities

Reports supported operations and real ffprobe dependency health without performing media work, helping you verify readiness before media tasks.

Instructions

Report implemented operations and real ffprobe dependency health; no media work.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo
successYes
project_idNo
request_idNo
storyline_idNo
schema_versionNo1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations present, the description must carry behavioral disclosure; 'Report ... health' and 'no media work' signal a read-only diagnostic with no side effects on media. It stops short of stating permissions, cost, or that the check touches only the runtime ffprobe binary.

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

Conciseness4/5

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

A single front-loaded sentence with no filler, though the telegraphic phrasing ('real ffprobe dependency health') is terse enough that the meaning of 'real' requires a moment to parse.

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?

A zero-parameter diagnostic with an output schema has little left to explain; the description correctly scopes it as a self-check rather than media work. The one residual ambiguity is what 'implemented operations' enumerates.

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 nothing for the description to disambiguate; the baseline of 4 applies.

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

Purpose4/5

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

Names a specific verb and resource: it reports which operations are implemented and the health of the ffprobe dependency. The trailing 'no media work' separates it from the media/probe siblings, though 'implemented operations' stays slightly abstract.

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?

The phrase 'no media work' implies an exclusion (don't call this to probe actual media), but no alternative is named and there is no explicit when-to-use framing such as diagnosing missing capabilities before invoking a job tool.

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