Skip to main content
Glama

studio_capture_viewport

Capture only the Roblox 3D viewport as a private local PNG without desktop or Studio panels. Never opens a permission prompt.

Instructions

Capture only the Roblox 3D viewport as a private local PNG without desktop or Studio panels. Never opens a permission prompt.

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

Input Schema

NameRequiredDescriptionDefault
widthNo
heightNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.3

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden, and it does add real value: the output is private and local, no permission prompt appears, and desktop/panels are excluded. However, it says nothing about where the PNG is written, what the return value is, or whether Studio/a playtest session must be running — significant gaps for a tool with zero annotation coverage.

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?

Two short sentences, front-loaded with the primary action and followed by the scope constraint. No filler.

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?

For a simple two-optional-parameter tool this is close, but with no output schema the description should disclose the return value (file path/format) and default capture dimensions, neither of which appear. The privacy/no-prompt note is helpful but not sufficient on its own.

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 two parameters, so the description must compensate, yet it never mentions width or height, their ranges, or what happens when they are omitted (both are optional). Naming aside, an agent gets no guidance on output resolution behavior.

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 ('capture the Roblox 3D viewport as a PNG') and narrows scope explicitly ('only the viewport... without desktop or Studio panels'). It doesn't name a sibling or clarify how it differs from something like studio_visual_probe, so sibling differentiation is left implicit.

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

Usage Guidelines3/5

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

The scoping phrase 'without desktop or Studio panels' implies you should use this when you want a clean viewport-only image, but there is no explicit when-to-use/when-not statement and no named alternative among the many studio_* siblings.

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