Skip to main content
Glama

capture_scene_preview

Capture a preview image of the current 3D scene for visual inspection and verification, with an optional maximum image size.

Instructions

Capture a scene preview 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_scene_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.4/5.0
Behavior2/5

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

With no annotations supplied, the description bears the full disclosure burden and gives essentially none: it does not say whether the capture triggers a render (costly) or is a fast viewport grab, whether it writes a file to disk or returns image data, or what format and resolution constraints apply. Only the existence of an output schema relieves it of describing the return payload.

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

Conciseness3/5

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

The single sentence is front-loaded and free of padding, but its brevity is a product of under-specification rather than efficiency. There is no second clause or qualifier to anchor the action to a scene-context or a maximum-size behavior.

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 tool in a crowded family of capture/render siblings with an undocumented parameter and no annotations, the definition is not complete enough. The output schema covers return values, but the missing differentiation, preconditions, and parameter meaning leave real gaps an agent would need to guess around.

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 0% schema description coverage, so the schema provides only a name and a null default. The description never mentions it, so the agent cannot learn whether it is pixels, a dimension cap, a bounding-box limit, or which axis it constrains.

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 scene preview image'), so the basic action is clear. However, it does not distinguish this from near-identical siblings such as 'capture_material_preview', 'render_preview', 'capture_viewport' or 'capture_camera_view', leaving the agent unable to tell which capture tool to pick when several could plausibly apply.

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 mention of preconditions (e.g. an active scene, a configured render engine, or a camera), and no reference to alternatives among the many sibling capture tools. The agent must infer everything from the one-line name expansion.

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