Get the full project structure with file tree and statistics.

Call this first when starting work on a project to understand its overall shape, module layout, and code distribution.

Get comprehensive context for a function: signature, parameters, callers, callees, dependencies, and docstring.

Supports 'ClassName.method_name' syntax (e.g., 'ToolExecutor.execute'). For two top-level functions sharing the same name in different files (where ClassName.method doesn't apply), pass file_path to pick one. If multiple matches remain, returns a disambiguation list.

Use this when you need to understand what a function does, who calls it, and what its blast radius is for modifications.

Get comprehensive context for a file: functions, classes, imports, and relationships to other files.

Use this when you need to understand what a file contains and how it connects to the rest of the codebase.

Get comprehensive context for a class: methods, properties, inheritance chain, and usages throughout the codebase.

Use this when you need to understand a class's interface and where it is used.

Get an overview of all symbols in a directory/package.

This is the intermediate zoom level between get_project_skeleton (whole project) and get_file_context (single file). Use it to understand what a package contains before drilling into specifics.

Find functions, classes, and files related to a natural language description.

Use this when you know WHAT you're looking for conceptually but not WHERE it lives in the codebase. Prevents duplicating existing functionality.

Find files related to a natural language description by scoring symbols inside them.

Use this when you need to understand which files are relevant to a feature or concept. Returns files grouped with their matching symbols.

Get the dependency graph for a symbol: what it depends ON and what depends on IT, up to the specified depth.

Use this to understand the impact radius of changing a symbol.

Get the call graph for a function: what it calls and what calls it, recursively up to the specified depth.

Supports 'ClassName.method_name' syntax (e.g., 'SkillManager.initialize'). If multiple functions share the same name, returns a disambiguation list.

Use this to trace execution flow and understand how a function fits into the larger call chain. By default, Python builtins and common stdlib methods (len, append, strip, etc.) are filtered out for clarity. Set include_builtins=True to see everything.

Set or change the project directory that Grafyx analyzes.

Call this when Grafyx reports 'No project loaded' — typically when running as a global MCP server. Pass the workspace root path.

After calling this, all other Grafyx tools will work on the specified project. Re-call with a different path to switch projects.

Detect and report coding conventions used in this codebase.

Use this to understand the project's style BEFORE writing new code, so your additions are consistent with existing patterns.

Force a full re-parse of the entire codebase graph.

Use this after making significant changes to the codebase, or if the graph seems stale. Normally the file watcher handles this automatically.

Find functions and classes with zero inbound references (dead code detection).

Analyzes the caller index and import graph to identify symbols that are never called, subclassed, or referenced from other code.

Excludes common false positives: dunder methods, framework-decorated handlers, entry points, and exception classes.

Find all classes that extend a given class, recursively.

Use this to understand the impact of changing a class's interface: which subclasses would need updating?

Supports multi-level inheritance trees up to the specified depth. When the codebase has multiple classes sharing class_name (e.g. Django defines Field in both contrib/gis/gdal/field.py and db/models/fields/__init__.py), pass file_path to pick the intended definition. Without it, the first match wins and the response includes ambiguous: True plus a candidates list so you can retry.