Skip to main content
Glama

unreal_capture_screenshot

Captures a screenshot of the Unreal Engine viewport for visual inspection, documentation, or sharing.

Instructions

Capture a high-quality screenshot.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "params": "<params>"
    },
    "name": "unreal_capture_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about where the image is written, what format or resolution is used, or whether the file is saved to disk versus returned inline. The one behavioral fact an agent needs most – how to retrieve the resulting screenshot – is absent.

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?

One short, front-loaded sentence with no wasted words, which is structurally clean. However, the brevity crosses into under-specification rather than economy, so conciseness does not compensate for the missing content.

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 whose only input is an undocumented nested object, the description should at minimum explain the expected params contents and where the captured file lands. An output schema exists so return-value detail is not required, but the input side and file-location behavior remain entirely unexplained.

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

Parameters1/5

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

The single required parameter is literally named "params" with 0% schema description coverage, making it completely opaque. The description adds no information about what must be supplied in that object, so the agent cannot construct a valid call from either source.

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 verb+resource pair ("capture a screenshot") is identifiable, but "high-quality" is undefined marketing phrasing that conveys no technical meaning. No distinction is drawn from the obvious sibling unreal_capture_viewport, so an agent cannot tell which capture tool to pick from the description alone.

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 prerequisites (e.g. an open editor, a target viewport), and no reference to alternatives such as unreal_capture_viewport. The description is a bare capability statement with no routing information.

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