Skip to main content
Glama
AnkleBreaker-Studio

Unity MCP Server

by AnkleBreaker-Studio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

unity_screenshot_scene

Capture a screenshot from the Unity Scene View camera and return its saved file path for scene review or documentation.

Instructions

Capture a screenshot of the Scene View camera. Returns immediately with the saved file path.

Input Schema

NameRequiredDescriptionDefault
pathNoSave path (default: Assets/Screenshots/SceneView_timestamp.png)
portNoUnity instance port (from unity_select_instance). Always include it when multiple instances run.
widthNoWidth 1-8192 (default 1920), at most 33554432 pixels total.
heightNoHeight 1-8192 (default 1080).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv2.36.0
    • changedInput schema / properties / height / description
      Previous value: -"Image height (default: 1080)"New value: +"Height 1-8192 (default 1080)."
    • addedInput schema / properties / height / maximum
      Added value: +8192
    • addedInput schema / properties / height / minimum
      Added value: +1
    • changedInput schema / properties / width / description
      Previous value: -"Image width (default: 1920)"New value: +"Width 1-8192 (default 1920), at most 33554432 pixels total."
    • 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.3/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 usefully discloses that the call is non-blocking ('Returns immediately') and what it yields (a saved file path), but says nothing about permissions, editor/play-mode requirements, or whether the returned path is guaranteed to exist yet.

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 tightly written sentences with the core action front-loaded and the return behavior second. Nothing is wasted or redundant.

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 low-complexity capture tool it covers the essential action and return value, and no output schema means explaining the return is appropriate. However, it omits any disambiguation from the three closely related capture siblings, which is the main thing an agent needs here.

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%, so all four parameters (path, port, width, height, including defaults and the 8192/pixel limits) are already documented in the schema. The description adds no additional parameter meaning, so the baseline of 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?

States a specific verb (Capture) and resource (screenshot of the Scene View camera), which does separate it from the game-view and editor-window siblings. It is clear what it does, though it never explicitly contrasts itself with unity_screenshot_game or unity_screenshot_editor_window.

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 alternatives, and no prerequisites (e.g. editor state, play mode, focused window). With three sibling capture tools present, the agent is left to infer selection entirely.

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