Skip to main content
Glama

renderdoc_check_available

Verify RenderDoc installation status on your system to enable graphics debugging and capture file analysis.

Instructions

Check if RenderDoc is available on the system. Returns availability status and installation info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Main handler for renderdoc_check_available tool. Checks RenderDoc availability using wrapper.is_available() and returns formatted response with availability status, native module info, and renderdoccmd path.
    if name == "renderdoc_check_available":
        available = wrapper.is_available()
        result = {
            "available": available,
            "native_module": wrapper._use_fallback is False,
            "renderdoccmd_path": getattr(wrapper, '_renderdoccmd', None),
        }
        return [TextContent(
            type="text",
            text=f"RenderDoc Availability:\n"
                 f"- Available: {available}\n"
                 f"- Native Python Module: {not wrapper._use_fallback}\n"
                 f"- renderdoccmd Path: {result['renderdoccmd_path'] or 'Not found'}"
        )]
  • Tool registration in the TOOLS list. Defines the renderdoc_check_available tool with its name, description, and input schema (empty object with no required fields).
    TOOLS = [
        Tool(
            name="renderdoc_check_available",
            description="Check if RenderDoc is available on the system. Returns availability status and installation info.",
            inputSchema={
                "type": "object",
                "properties": {},
                "required": [],
            },
        ),
  • The is_available() method in RenderDocWrapper that performs the actual availability check by checking if native renderdoc module is available or if renderdoccmd executable was found.
    def is_available(self) -> bool:
        """Check if RenderDoc is available."""
        return RENDERDOC_AVAILABLE or self._renderdoccmd is not None
  • The _find_renderdoccmd() helper method that searches for the renderdoccmd executable in common installation paths and PATH environment, used as fallback when native module is not available.
    def _find_renderdoccmd(self) -> Optional[str]:
        """Find renderdoccmd executable."""
        # Common installation paths on Windows
        common_paths = [
            os.environ.get("RENDERDOC_PATH", ""),
            "C:\\Program Files\\RenderDoc\\renderdoccmd.exe",
            "C:\\Program Files (x86)\\RenderDoc\\renderdoccmd.exe",
        ]
    
        for path in common_paths:
            if path and os.path.exists(path):
                if os.path.isdir(path):
                    cmd_path = os.path.join(path, "renderdoccmd.exe")
                    if os.path.exists(cmd_path):
                        self._renderdoccmd = cmd_path
                        return cmd_path
                else:
                    self._renderdoccmd = path
                    return path
    
        # Try to find in PATH
        try:
            result = subprocess.run(
                ["where", "renderdoccmd"],
                capture_output=True,
                text=True
            )
            if result.returncode == 0:
                self._renderdoccmd = result.stdout.strip().split("\n")[0]
                return self._renderdoccmd
        except Exception:
            pass
    
        self._renderdoccmd = None
        return None
  • The call_tool decorator that routes all tool invocations, including renderdoc_check_available, to their respective handlers based on the tool name.
    @server.call_tool()
    async def call_tool(name: str, arguments: dict[str, Any]) -> list[TextContent]:
        """Handle tool invocations."""
        wrapper = get_wrapper()
    
        try:
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 that the tool returns 'availability status and installation info', which gives some behavioral insight into what to expect. However, it lacks details on potential errors (e.g., if RenderDoc is not installed), performance implications, or system requirements, leaving gaps in behavioral context.

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?

The description is a single, well-structured sentence that efficiently conveys the tool's purpose and expected output. It is front-loaded with the main action ('Check if RenderDoc is available') and avoids unnecessary details, making it easy to understand quickly without wasted words.

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?

Given the tool's low complexity (0 parameters) and no output schema, the description is moderately complete. It explains what the tool does and what it returns, but without annotations or an output schema, it lacks details on the format of the return values (e.g., what 'availability status' includes) and error handling, which could be helpful for an AI agent.

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 input schema has 0 parameters with 100% coverage, meaning no parameters are documented in the schema. The description does not mention any parameters, which is appropriate here. It adds value by explaining the tool's purpose and return information, compensating for the lack of parameter documentation in the schema.

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?

The description clearly states the specific action ('Check if RenderDoc is available') and the resource ('on the system'), with explicit mention of what it returns ('availability status and installation info'). It distinguishes itself from sibling tools like 'renderdoc_analyze_draw_call' or 'renderdoc_open_capture' by focusing on system availability rather than capture analysis or manipulation.

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?

The description implies usage context by stating it checks 'availability on the system', suggesting it should be used to verify RenderDoc installation before attempting other operations. However, it does not explicitly state when not to use it or name specific alternatives among siblings, such as using this tool first before invoking others that require RenderDoc to be available.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

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