IdencifyDocs / Tools
The 14 tools
Every tool answers a question the open file can't. All of them run against the indexed graph — answers are backed by real relations, not text matching.
Change code safely
analyze_impact
The blast radius of a change, before you make it. Given a symbol, it walks the graph transitively (calls, containment, implementations, extensions) and returns everything that could break, ranked, with the total count even when the list is truncated. This is the tool that turns "rename and pray" into an informed decision.
expand_call_graph
Callers and callees N levels deep from any symbol, across files and across languages. Use it when you need the shape of a flow — who feeds this function, what it fans out to — rather than the full impact set.
get_definition
The definition of a symbol plus its dependency context, resolved by the graph (not by guessing from names). Depth is configurable, so an agent can pull exactly as much surrounding context as the task needs.
check_boundaries
Architecture-boundary violations: dependencies that cross module lines they shouldn't, with severity. Useful as a pre-merge check when an agent has been editing across a large codebase.
Find things
symbol_search
Hybrid search over the whole repo: semantic understanding for meaning, keyword matching for precision, and exact-identifier matching so searching for a symbol name always hits it.
find_pattern
Structural pattern occurrences across the repository — deterministic and complete, where grep gives you text matches with false positives in strings and comments.
get_context
A ranked, assembled context pack for a task: the symbols, definitions and relations an agent should read first, sized to fit a context window instead of flooding it.
summarize_file
A file's summary with its symbols and their relations — the fast way for an agent to orient in an unfamiliar file without reading all of it.
Repository health
health_score
A graded health report (A–F) with the specific hotspots that drag the grade down: dead code candidates, cycle counts, boundary violations, oversized modules. Point an agent at the hotspots and let it work through them.
detect_cycles
Dependency cycles ranked by severity, with member lists. Cycles are where refactors go to die — knowing them before an edit saves hours.
History and change
graph_diff
An exact structural diff between two commits: symbols added and removed, relations that appeared or vanished, breaking-change candidates — computed from the graph itself, not approximated from text diffs.
semantic_changelog
A human-readable changelog derived from graph changes: new dependencies, removed public API, signature changes flagged as potentially breaking only when the graph shows an actual removal.
search_history
Query the indexed git history — which commits touched a symbol, when a relation appeared — without shelling out to git.
Feedback loop
rate_context
Agents (or you) rate retrieved context, and the ranking learns from it. The retrieval quality you get in month two is better than day one.