Find where a feature or symbol lives in ONE call: ranked hits with their summaries, plus a source snippet of the top hit to confirm. Start here for "where is X" / "where do we do Y" — usually all you need; no setup call required first.

Where does a feature BEGIN? Returns the entry/boundary that dominates the feature (route handler, CLI command, main, or exported API) — its file is where to start reading — plus the call path down through it. Use for "where do I start to understand X"; for "where is symbol X defined" use locate.

Hybrid (semantic + symbol) ranked summaries — NOT source. Returns several candidates without snippets; prefer locate when you just need to find one thing.

A node's generated summary/context (title, summary, description, signature, domain, keywords). Pass id for one, or ids to fetch several in one turn.

Raw source for a node — the deliberate 'expensive' read. locate already includes a snippet of the top hit, so you often don't need this. Pass id for one, or ids for several.

All adjacent nodes of an id, grouped by edge family (calls, imports, contains, related, …).

BFS up to k hops along ONE edge family (e.g. calls) from a node.

The routing table: file/package summaries ranked by PageRank, packed to a token budget. Reach for it to orient on an unfamiliar repo.

A node's k-hop dependency neighborhood, source packed in topological order to a token budget (the single-shot static fallback).

Optional ~100-token orientation: stats + the top nodes by importance. Call only if you want a quick lay of the land — it is NOT a prerequisite for the other tools.