Skip to main content
Glama

qa_check

Read-only

Verify a finished video render for format, duration, black frames, dead air, loudness, and hook timing; returns a contact sheet, post-cut frames, and a jobId.

Instructions

Check a finished render: format, duration, black frames, dead air, loudness, hook timing; returns a contact sheet and frames after the first cuts. Returns a jobId.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "renderId": "<renderId>"
    },
    "name": "qa_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNo
renderIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe non-mutating operation, and the description adds useful detail about the artifacts produced (contact sheet, frames after first cuts). However, 'Returns a jobId' signals asynchronous execution without saying how to collect the result, and the presence of a bounded `wait` parameter is never explained, leaving the async contract ambiguous.

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?

Two compact sentences with the verification scope front-loaded and no filler. The only weakness is the redundant return phrasing — the contact sheet/frames clause and the trailing 'Returns a jobId.' could be merged into one return statement.

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?

There is no output schema, so the description must describe return values, and it does name the concrete deliverables plus the jobId. What is missing is the follow-up path: nothing says the agent must poll job_status with that jobId to retrieve results.

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?

With schema description coverage at 0%, the description carries the burden and largely does: 'a finished render' makes the required renderId unambiguous, and 'returns a contact sheet and frames' explains what the call ultimately yields. It says nothing about `wait` (0-45s, default 30), so that parameter's blocking semantics remain opaque.

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?

The description gives a specific verb and resource ('Check a finished render') and then enumerates exactly what is verified: format, duration, black frames, dead air, loudness, hook timing. That scope is far more concrete than a sibling like timeline_validate or media_inspect, though it never explicitly names which sibling covers the pre-render or single-asset case.

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?

'Check a finished render' implies the timing (after a render exists), but there is no explicit statement of when to use this versus timeline_validate, media_inspect, or analyze, and no stated prerequisites. Usage is inferable rather than directed.

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