Skip to main content
Glama

capture_material_preview

Captures a material preview viewport image from Blender so you can visually verify shader and material results in AI-driven 3D workflows.

Instructions

Capture a material preview viewport image.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "capture_material_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_sizeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full behavioral burden and it discloses almost nothing: no prerequisites, no statement of which material is captured, no format or size behavior, no mention that the viewport must be in material preview mode. Only the existence of an output schema spares it a lower score.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; nothing is wasted, but at this length the terseness reflects under-specification rather than efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a capture tool with no annotations, an undocumented size parameter, and ambiguity about which material it targets, the description is far too thin. The output schema covers return values, but the agent still cannot tell what state the tool requires or what it will actually image.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter max_size has a null default and 0% schema description coverage, so neither schema nor description explains what it bounds (pixels per side? longest edge? percentage?) or what the default behavior is when it is null. The description does not compensate for this gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: capture a material preview viewport image. It is a clear action, though it does not distinguish itself from the many sibling capture_* tools (capture_scene_preview, capture_camera_view, render_preview) beyond the word 'material'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance at all. It never says whether the active material, a selected material, or a material identified elsewhere is captured, nor when to prefer this over capture_scene_preview or render_preview.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools