Find code by NAME, CONTENT, or MEANING — the one way in (default limit 25). Returns graph nodes WITH their signatures (not dead text lines): often enough to answer without info(). Pass any node to relations/info. Use wherever you'd grep or search for a symbol; content hits fold into the enclosing symbol. text_matches = non-symbol hits. Content is matched LITERALLY (not regex) — write 'Request(' or 'getErrorMap(' as-is, no escaping needed. Scope with path_glob (e.g. 'tests/', '.ts', '!tests/' to exclude) — there is no file:/content: query syntax, so use this instead of guessing one. Test files are excluded by default unless you set path_glob yourself or the query says 'test' — pass path_glob='tests/' to search them on purpose. For 'list EVERY file that calls/imports X' — where the top-N node list could miss some — set exhaustive=true: returns every matching file path (no signatures), uncapped by the normal limit. If the response's note field is set, your exact text matched nothing — every node is a name/meaning guess, not a confirmed hit — simplify the query instead of repeating it.

A symbol's neighbourhood in one call: who calls it, what it calls, what implements/subclasses it, and non-call references — each with its signature. Accepts a node id OR a name (default depth 2, limit 25). THE tool for impact analysis and 'what implements X'. If the name matches several definitions, pass file (a path or suffix) to pin the right one — e.g. one UserService per service in a monorepo.

Read a specific target. A SYMBOL (node id or name) -> source, signature and location. A FILE path -> its symbol outline by default (default limit 200 symbols) — a cheap structural overview. Set mode='source' to read the file's actual current content instead: line-numbered (same shape as Read, safe to Edit from), windowable with offset/limit exactly like Read, plus which files import it. Use mode='source' instead of opening the file yourself whenever you need the body, not just its symbol list. If a symbol name matches several definitions, pass file (a path or suffix) to pin the right one — e.g. one UserService per service in a monorepo.