Loading ToolBench
Local MCP server for KeyShot product visualization, scene editing, camera control, and rendering.
KeyShot MCP has 19 well-structured tools with complete input schemas and descriptions. Naming follows verb_noun convention (render, import, apply, list, set). Descriptions are present and actionable (avg ~120 chars). However, parameter descriptions are often generic ('Path to the KeyShot scene file' repeated 12+ times), and output schemas are not documented in the source. Error handling is minimal, no recovery guidance, retryability classification, or actionable error messages visible. Tool composition is sound (single responsibility), but some tools could be consolidated (e.g., render, batch_render, render_all_cameras, render_queue overlap in intent). Security: no secrets in params (good), but no audit logging or permission gates visible.
Apply a camera preset to a KeyShot scene.
Apply a material to an object in a KeyShot scene.
Apply a material preset to an object in a KeyShot scene.
Render multiple cameras from a KeyShot scene in batch mode.
Import a 3D model file into KeyShot and create a new scene.
Inspect a KeyShot scene to discover objects, cameras, materials, and environments.
List all available camera presets.
Output schemas not documented. Tool descriptions state what they do but do not specify return structure (fields, types, pagination). LLMs cannot plan downstream calls or extract required data without knowing response shape.
Render tool family overlap (render, batch_render, render_all_cameras, render_queue, product_render). Four tools do similar work with different parameter shapes. LLMs waste reasoning cycles choosing between them. Consider consolidating into one render tool with flexible camera selection.
Parameter descriptions are generic and repetitive ('Path to the KeyShot scene file' appears 12+ times). Descriptions should explain WHEN to use each parameter, what values are valid, and dependencies. E.g., 'scenePath: Path to the .ks scene file. Required unless modelPath is provided.'
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 69 | 2025-06-18+ | v2 |
List all cameras in a KeyShot scene.
List all available material presets.
Render a quick preview of a KeyShot scene and return the image as base64-encoded content.
Render a KeyShot product scene with automatic setup and quality presets.
Render a single image from a KeyShot scene with specified camera and quality settings.
Automatically discover and render all cameras in a KeyShot scene.
Render multiple images from a KeyShot scene in a queue with different cameras and settings.
Save a KeyShot scene to a file.
Modify camera properties in a KeyShot scene.
Modify environment properties in a KeyShot scene.
Check KeyShot MCP server status and diagnostic information.
Synchronize a KeyShot scene file that was edited in the GUI with the MCP server's working directory.
No error handling guidance visible. Tools do not document what errors are retryable, what user input is needed, or how to recover. E.g., 'File not found' should suggest 'Check the path or call keyshot_inspect_scene to list available scenes.'
Tool annotations present (readOnlyHint, destructiveHint) but not visible in source code. Verify that all WRITE tools (import_model, apply_material, render, set_camera, save_scene) are marked destructiveHint=true and all READ tools marked readOnlyHint=true.