Skip to main content
Glama
Sign In
Daz3D-MCP

Daz3D-MCP

by MictlanLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

viewport_capture

Read-onlyIdempotent

Capture an image of the active 3D viewport to inspect the scene, optionally at a chosen timeline frame, through a specified camera, and at a set maximum resolution.

Instructions

Returns an image of the active 3D viewport so you can see the scene.

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": "viewport_capture"
  }
}

Input Schema

NameRequiredDescriptionDefault
frameNoTimeline frame to show.
cameraNoCamera label to look through; default is the viewport's.
max_sizeNoLongest side in pixels.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds only that the output is an image of the *active* viewport, without saying whether the viewport must be open/visible, what image format is returned, or whether capture is expensive. Useful but thin given the low bar set by annotations.

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

Conciseness5/5

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

One front-loaded sentence with zero wasted words, stating output and intent immediately.

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

Completeness4/5

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

For a simple, fully-annotated read tool with a fully documented three-parameter schema and no output schema, the description covers the essentials: what comes back and what it depicts. The only gap is operational context such as whether the viewport must be active or how capture interacts with camera overrides.

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

Parameters3/5

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

Schema description coverage is 100% and all three parameters (frame, camera, max_size) have defaults and bounds documented in the schema. The description adds nothing about parameters, which is acceptable but not additive, so the baseline 3 applies.

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?

The description states a specific verb and resource ('Returns an image of the active 3D viewport') plus the intent ('so you can see the scene'), which lets an agent tell it apart from the anim_* and camera_* siblings. It stops short of naming a sibling it differs from, so it lands at 4 rather than 5.

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 explicit when-to-use or when-not-to-use guidance and no alternative named. The phrase 'so you can see the scene' only implies a visual-verification use case; an agent must infer whether this replaces or complements camera_shot or anim_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