No user-submitted related servers found.
Scored across 4 tools
Each tool targets a clearly different part of the pipeline: environment inspection, script execution, knowledge lookup, and spec validation. There is no practical overlap, and descriptions make the boundaries explicit (e.g., execute vs. validate operate on scripts vs. specs).
Three tools follow a clean verb_noun pattern (execute_blender_pass, query_blender_knowledge, validate_part_spec) with a shared snake_case convention. blender_runtime_status is a noun-phrase status probe rather than an action verb, a minor but noticeable deviation from the otherwise predictable pattern.
Four tools is on the lean side but each maps to a distinct stage of the headless Blender workflow. Nothing feels redundant or padded, though the surface is minimal enough that a slightly richer set would be expected for the stated scope.
The core loop is covered: check the environment, consult the knowledge base, run bpy scripts, and validate output specs. Minor gaps exist — there is no tool to author or repair a spec, enumerate knowledge topics, or inspect/render resulting assets beyond the AGENT_OK sentinel — but agents can work around these via script execution.