No user-submitted related servers found.
Scored across 6 tools
Tools are mostly distinct by lifecycle stage: stg_account and stg_pricing cover license/commercials, stg_spend_report covers spend, stg_inspect_render measures technical quality, stg_detect_events finds edit points, and stg_qa_gate makes the final decision. stg_inspect_render and stg_detect_events both analyze video frames, but their outputs and stated uses differ clearly enough.
All tools use the same stg_ prefix and snake_case casing, so the naming is predictable. Names mix verb_noun (stg_inspect_render, stg_detect_events) with noun_phrase labels (stg_account, stg_pricing), but that is a minor deviation rather than an inconsistent convention.
Six tools are well-scoped for a render QA/guarding workflow, with each tool covering a distinct stage: account, pricing, spend, technical inspection, event detection, and final gate. The count is neither thin nor bloated.
The surface covers license status, pricing, spend tracking, technical render inspection, event detection, and a QA decision gate, which is a coherent lifecycle. Minor gaps remain around license activation/configuration and any explicit semantic-defect helper, but agents can work around these by supplying license state and semantic notes themselves.