From 0c451a447c987e3139c8d1a5df2aaaa0bbe8a678 Mon Sep 17 00:00:00 2001 From: Teal Bauer Date: Tue, 11 Nov 2025 13:43:35 +0100 Subject: [PATCH] docs: clarify max_depth parameter for call graph analysis Improve documentation to make it clear that max_depth can be increased for deeper call chains. This helps AI models understand when and how to use larger depth values. Refs #8 --- bridge_mcp_hydra.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/bridge_mcp_hydra.py b/bridge_mcp_hydra.py index 1e33689..590a3c0 100644 --- a/bridge_mcp_hydra.py +++ b/bridge_mcp_hydra.py @@ -1944,13 +1944,13 @@ def analysis_run(port: int = None, analysis_options: dict = None) -> dict: @mcp.tool() def analysis_get_callgraph(name: str = None, address: str = None, max_depth: int = 3, port: int = None) -> dict: """Get function call graph visualization data - + Args: name: Starting function name (mutually exclusive with address) address: Starting function address (mutually exclusive with name) - max_depth: Maximum call depth to analyze (default: 3) + max_depth: Maximum call depth to analyze (default: 3). Increase for deeper call chains (e.g., 10-15 for complex functions) port: Specific Ghidra instance port (optional) - + Returns: dict: Graph data with nodes and edges """