Skip to main content
Glama

renderdoc_analyze_draw_call

Analyze a specific draw call to examine input/output resources, shaders, and state for graphics debugging in RenderDoc captures.

Instructions

Perform detailed analysis of a specific draw call including input/output resources, shaders, and state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_idYesThe event ID of the draw call to analyze.

Implementation Reference

  • Tool registration defining the renderdoc_analyze_draw_call tool schema with name, description, and inputSchema (requires event_id parameter)
    Tool(
        name="renderdoc_analyze_draw_call",
        description="Perform detailed analysis of a specific draw call including input/output resources, shaders, and state.",
        inputSchema={
            "type": "object",
            "properties": {
                "event_id": {
                    "type": "integer",
                    "description": "The event ID of the draw call to analyze.",
                },
            },
            "required": ["event_id"],
        },
    ),
  • Handler implementation that checks if capture is open, validates event_id parameter, and returns stub message indicating functionality is not yet implemented
    elif name == "renderdoc_analyze_draw_call":
        if not wrapper.current_file:
            return [TextContent(type="text", text="Error: No capture is currently open.")]
    
        event_id = arguments.get("event_id")
        if event_id is None:
            return [TextContent(type="text", text="Error: event_id is required")]
    
        # Draw call analysis requires more complex implementation
        return [TextContent(type="text", text="Draw call analysis is not yet implemented.")]

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Hengle/Renderdoc-Mcp2'

If you have feedback or need assistance with the MCP directory API, please join our Discord server