Skip to main content
Glama

capture_wireframe

Capture a wireframe viewport image from Blender to inspect geometry and verify modeling structure before shading or rendering.

Instructions

Capture a wireframe 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_wireframe"
  }
}

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.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing about whether a file is written to disk, where it is written, what format, whether it is destructive, or whether a scene/context must be active. The single sentence adds no behavioral context beyond the name.

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 short, front-loaded sentence with no filler; it is efficient, though the terseness comes at the cost of substance.

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

Completeness3/5

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

An output schema exists, so return values need not be explained. Still, for a capture tool with an entirely undocumented parameter and zero annotations, the definition leaves the agent without enough information to call it correctly versus siblings.

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?

Schema description coverage is 0% for the sole parameter 'max_size' (nullable integer, default null), so the description must compensate and does not. It does not say whether max_size is pixels per side, a bounding dimension, a file-size cap, or how the aspect ratio is preserved.

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

Purpose3/5

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

The description states a specific verb and resource ('Capture a wireframe viewport image'), which is clearer than the title-less name alone. However it does not distinguish this from the many sibling capture tools (capture_viewport, capture_render, capture_camera_view, capture_multiple_angles, etc.), and it never defines what a 'wireframe' capture means visually, so the agent cannot confidently separate it from capture_viewport.

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?

There is no when-to-use guidance, no prerequisites, and no mention of any alternative. With a dense sibling cluster of capture_* tools, the absence of any routing signal is a real gap.

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