Skip to main content
Glama

capture_renderdoc_frame

Trigger a RenderDoc frame capture in the O3DE editor and report the result; if the API cannot trigger it, provide manual capture alternatives such as F12 or the GPU capture menu.

Instructions

Trigger a RenderDoc frame capture in the O3DE editor.

Attempts to trigger a RenderDoc capture via GraphicsProfilerBus. That bus is not exposed to editor Python on O3DE 26.10.0, so there the tool returns manual_required with the manual alternatives (F12 in RenderDoc, or the editor's GPU capture menu).

Returns: JSON with status ok if the capture was triggered, error on failure, or manual_required if the Python API cannot trigger the capture and manual action is needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does so well: it discloses the underlying bus dependency, the version-specific limitation, and the exact failure mode (manual_required with fallbacks). It does not mention whether the capture affects editor state or performance, a minor remaining gap.

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?

Front-loads the purpose in the first sentence, then layers mechanism, limitation, and return behavior in short, well-structured paragraphs. No filler sentences.

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

Completeness5/5

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

For a parameterless capture tool, the description covers the trigger mechanism, the environment-specific caveat, and the fallback path. An output schema exists, so the added Returns section is bonus context rather than a required burden.

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

Parameters4/5

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

The tool takes zero parameters, so per the rubric the baseline is 4; there is nothing to document and the description adds no misleading parameter information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Trigger') and resource ('RenderDoc frame capture') scoped to the O3DE editor, and the mechanism (GraphicsProfilerBus) is named. It is clearly distinguishable from siblings like capture_viewport and get_scene_snapshot.

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

Usage Guidelines4/5

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

Explains the conditions under which the tool works versus fails (bus not exposed on O3DE 26.10.0) and points to the manual alternatives (F12, GPU capture menu). It gives clear context for invocation, though it does not explicitly compare itself against a sibling tool.

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