Skip to main content
Glama

video_doctor

Read-onlyIdempotent

Returns a read-only JSON readiness verdict for the next video job, so AI agents can verify prerequisites before starting an edit.

Instructions

Return a read-only JSON readiness verdict for the next video job.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.0
    • removedInput schema / properties / overwrite
      Removed value: -{
      -  "default": false,
      -  "description": "Explicitly allow replacing existing media. Existing non-media files are protected.",
      -  "title": "Overwrite",
      -  "type": "boolean"
      -}
    • removedInput schema / title
      Removed value: -"video_doctorArguments"
    • removedOutput schema / title
      Removed value: -"video_doctorDictOutput"
  2. Addedv1.16.5

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so "read-only" in the description is largely redundant. What the description does add is that it assesses the next job's readiness rather than the media itself, but it does not disclose what would make a verdict negative or whether it has side effects on job state.

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?

A single front-loaded sentence with no filler; every word (read-only, JSON, readiness, next job) carries signal. Nothing is padded or restated.

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?

The schema is empty and an output schema exists, so return values need not be explained, which lowers the bar considerably. Still, an agent cannot tell what conditions produce a not-ready verdict or what action should follow, which is the main thing a pre-flight tool needs to convey.

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 no parameters, so the baseline is 4; there is nothing for the description to disambiguate. The mention of a specific JSON verdict is consistent with the declared output schema.

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 concrete verb and output shape ("Return a read-only JSON readiness verdict") and scopes it to "the next video job," which separates it from informational siblings like video_info and from the operational siblings such as video_qc_ops. What constitutes "readiness" is left undefined, so the agent knows the form of the answer but not the checks behind it.

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 "for the next video job" implies a pre-flight gate to be called before executing a job, which is usable context. However, there is no explicit statement of when to call it versus video_info or video_qc_ops, and no exclusions or prerequisites are given.

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