No user-submitted related servers found.
Scored across 24 tools
Most tools target clearly distinct resources or lifecycle stages, and descriptions explicitly separate local from cloud and discovery from execution. Some potential confusion remains among noun-only multiplexed tools (rh_job, rh_work_item, rh_prepare_generation) and between validate_payload and validate_workflow, but boundaries are generally clear.
All tools use a consistent rh_ snake_case prefix, but the naming pattern is not uniform: many are verb_noun, while project, asset, scene, work_item, and job are noun-only tools that bundle multiple operations. The names are readable but do not follow one predictable convention.
24 tools is heavy for a single MCP server and sits at the upper edge of the 16-25 range before becoming excessive. The domain is broad enough that each tool has some rationale, but the set is large enough to burden selection and increase cognitive load.
The surface covers discovery, workflow creation/read/edit/validate/export/import/search, project and asset handling, scene and work-item context, generation preparation/run/job/results/review, and capability reporting. Some delete or list operations are absent, such as deleting projects/assets or listing jobs, but core generation lifecycle coverage is strong.