Tools
jump
Resolve visible symbols to authoritative definitions.
Use jump to follow source identifiers to definitions in the workspace, configured dependencies, or the standard library.
Use when
- You have a visible source occurrence and need its definition.
- You need an API outline or implementation for a resolved target.
Do not use when
- You know only a symbol name; use
grep_definition. - You need the body of an already discovered handle; use
extract.
Request
{"file":"/workspace/project/src/lib.rs","symbols":[["UserService",42]],"output_mode":"api","show_implementations":false,"workspace_root":"/workspace/project"}Parameters
| Field | Required | Default / bounds |
|---|---|---|
file | source form | Path; file_path is accepted as an alias. |
symbols | source form | Entries are [symbol_name, line]; line is a 1-based integer. |
handles | handle form | Registered handles; mutually exclusive with source fields. |
output_mode | no | api; union: api, implementation. |
show_implementations | no | false; enabling can be expensive for widely used traits/types. |
workspace_root | no | Source-form workspace routing. |
What it returns
Resolved definitions grouped by destination. api returns signatures, hierarchy, and declarations; implementation selects Code, falling back to Full, with inline type annotations. Missing outlines or code retain exact LSP-range fallbacks. Optional implementor/attached-implementation outlines are included when requested.
Common mistakes
- Using a guessed line or symbol spelling that is not visible at that location.
- Requesting
implementationafterapiwhen one implementation request would suffice. - Enabling
show_implementationsfor broad traits without needing the complete surface.
Related tools
grep_definition, extract, hover, show_usage