Loading ToolBench
MCP server for controlling local Photoshop on Windows via COM automation
Server has well-structured tool definitions with complete JSON schemas and clear descriptions. All 9 tools have explicit registrations with inputSchema, type constraints, and parameter descriptions. Naming follows verb_noun convention (photoshop_*). However, output schemas are not documented, LLMs cannot predict response structure. Parameter descriptions are present but often minimal (e.g., 'Optional COM ProgID override' lacks guidance on when/why to use it). No error handling guidance, no recovery patterns, and no documentation of what each tool returns. Missing descriptions for nested object properties (e.g., crop.left/top/right/bottom lack individual descriptions). Tool descriptions average ~120 chars, which is adequate but could be more prescriptive about prerequisites and side effects.
Create an editable Photoshop text layer in the active document.
Apply common edits to the active document, optionally opening and exporting a file.
Paste a transparent overlay image into the active document, set blend mode/opacity, and align its visible bounds.
Create a new Photoshop document with a specified canvas size, background, and resolution.
List Photoshop-related COM ProgIDs registered on Windows without launching Photoshop.
Open an image file in Photoshop and return document information.
Place a local image into the active document as a new layer, with optional position, scale, opacity, and blend mode.
No output schemas documented. LLMs cannot predict what fields each tool returns, forcing them to guess downstream field names and risk broken tool chains.
Nested object properties (e.g., crop.left, crop.top, crop.right, crop.bottom in photoshop_adjust_image; x, y in maskPolygons in photoshop_texture_recolor) lack individual descriptions. LLMs cannot infer what each coordinate represents.
No error handling guidance. Tools do not document what errors can occur, whether they are retryable, or what the LLM should do next (e.g., 'Photoshop not running, ensure it is installed and running on Windows').
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 60 | 2026-07-28+ | v2 |
Check whether local Photoshop can be reached and report the active document.
Recolor a selected region while preserving original texture, highlights, shadows, and feathered edges.
Parameter descriptions are minimal and lack context. E.g., 'Optional COM ProgID override' does not explain when to use it, what the default is, or what happens if it is wrong. Descriptions should be 50 - 200 chars and prescriptive.
No documentation of side effects or prerequisites. Tools like photoshop_open_image and photoshop_create_document modify state but descriptions do not explicitly say 'This creates a new document' or 'This opens a file and makes it active'.