MCP server for managing, creating, forking, and exporting WGSL shaders with support for multiple target formats (HLSL, Unity, Unreal, Blender, Three.js)
ShaderVine has well-structured tool definitions with consistent naming (verb_noun pattern), clear descriptions (avg 120 chars), and visible JSON Schema parameters. All 7 tools are explicitly registered with mcp.NewTool() in backend/internal/mcp/server.go. However, output schemas are not documented, handlers return JSON via mcp.NewToolResultText() without declaring expected response structure. Parameter descriptions are present but lack constraints (enums, ranges, format specs). Error handling returns generic error strings without recovery guidance. No tool annotations (readOnlyHint/destructiveHint) despite clear risk distinctions (5 READ_ONLY, 2 WRITE).
Create a new WGSL shader in ShaderVine. Provide the full fragment shader code.
Export a shader to a different format: wgsl, hlsl, unity, unreal, blender, or threejs
Fork an existing shader to create a new variant based on it
Get a specific shader by ID, including its WGSL code and uniforms
List all available shader categories and how many shaders are in each
List all shaders in ShaderVine, optionally filtered by category
Search shaders by name, tags, or description
Output schemas not documented. Handlers return JSON via mcp.NewToolResultText() without declaring expected response structure (fields, types, nesting). LLMs cannot plan downstream tool calls or extract data reliably.
Parameter constraints missing. 'category' accepts free-form strings instead of enum (generative|noise|material|fractal|post-fx). 'format' in export_shader lacks enum constraint. 'limit' has no min/max bounds. LLMs will hallucinate invalid values.
No tool annotations. Tools lack readOnlyHint/destructiveHint/idempotentHint despite clear risk profile (5 READ_ONLY, 2 WRITE). Agents cannot distinguish safe from destructive operations.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 66 | 2026-07-28+ | v2 |
Error handling lacks recovery guidance. Handlers return mcp.NewToolResultError() with generic messages ('Failed to list shaders: <err>') without actionable next steps or error classification (retryable vs user-fixable).
Pagination not implemented. list_shaders() caps results at 100 but offers no cursor/offset mechanism for large datasets. Agents cannot iterate through all shaders efficiently.