Skip to main content
Glama
AnkleBreaker-Studio

Unity MCP Server

by AnkleBreaker-Studio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

unity_graphics_scene_capture

Render the Unity Scene View camera to an inline PNG at specified dimensions, so you can inspect the editor scene directly in chat.

Instructions

Render the Scene View camera to inline PNG. Whole-pixel sizes within device limits, at most 33554432 pixels.

Input Schema

NameRequiredDescriptionDefault
portNoUnity instance port (from unity_select_instance). Always include it when multiple instances run.
widthNoImage width in pixels (default: 512)
heightNoImage height in pixels (default: 512)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.36.0
    • addedInput schema / properties / height / maximum
      Added value: +8192
    • addedInput schema / properties / height / minimum
      Added value: +1
    • addedInput schema / properties / width / maximum
      Added value: +8192
    • addedInput schema / properties / width / minimum
      Added value: +1
  2. Changed1 schema field changedv2.35.6
    • changedInput schema / properties / port / description
      Previous value: -"Target Unity instance port for parallel-safe routing. Get this from unity_select_instance. When working with multiple Unity instances, ALWAYS include this parameter."New value: +"Unity instance port (from unity_select_instance). Always include it when multiple instances run."
  3. Addedv2.28.1

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses useful constraints (whole-pixel sizes, device limits, 33554432-pixel cap) and the output format, but says nothing about side effects, blocking behavior, or error conditions when the Scene View is unavailable.

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?

Two compact sentences with the core action front-loaded and no filler. The second clause about pixel limits is slightly awkward but still earns its place as a constraint.

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?

With no annotations and no output schema, the description does at least name the return format (inline PNG). But for a capture tool it omits details like what the captured frame contains and instancing/multi-instance behavior, leaving gaps against the full burden.

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 coverage is 100%, so width/height/port are already fully documented in the schema. The description's mention of pixel limits adds only marginal value and does not map onto the specific parameters, so baseline 3 is appropriate.

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 (Render) plus resource (Scene View camera) and output format (inline PNG), which is clear. However, it offers no differentiation from the nearly identical sibling unity_screenshot_scene, leaving an agent unsure which capture tool to pick.

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 guidance on when to use this versus the many capture siblings (unity_screenshot_scene, unity_graphics_game_capture, unity_screenshot_game, unity_screenshot_editor_window). The description states what it does but never when or why to choose it.

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