Captures a Substance Painter viewport screenshot so you can inspect the 3D model or the full UI window.
Look at Painter. view="3d" is the model; view="window" includes the whole UI.
| Name | Required | Description | Default |
|---|---|---|---|
| view | No | 3d | |
| max_size | No |
Changes observed during successful MCP inspections.
v1.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about output format, whether an image is returned, or how max_size affects the result. The only content is a brief view-mode distinction.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is only two short sentences and contains no filler. However, its brevity reflects under-specification rather than tightly packed useful detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple two-parameter capture tool with no annotations or output schema, the description should at least state that it produces a viewport image and explain max_size. Neither is present, leaving meaningful gaps for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate for both parameters. It explains the view parameter's two values but says nothing about max_size, leaving half the parameters undocumented.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description says only 'Look at Painter,' which is vague and never states that the tool captures a screenshot/image of the viewport. It clarifies the view mode values but does not clearly distinguish the tool's core action from capture_turntable or capture_channel.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives such as capture_turntable or capture_channel. The view-mode distinction is useful but does not tell the agent when this capture is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.