MCP tools overview

Orstrum exposes eight tools over the Model Context Protocol. Path-taking tools accept source paths in absolute, cwd-relative, or repo/relPath shorthand form — agents never manage internal IDs.

The server runs locally via orstrum serve, or against the pushed cloud graph via orstrum serve --cloud. Both expose the same eight tools with identical input schemas and output shapes.

orstrum_get_summary LLM purpose + top callers and imports for a file orstrum_get_exports Exported symbols with kind and AST signature orstrum_get_imports Outbound imports with resolved cross-file edges orstrum_get_callers Every indexed file that imports a given file orstrum_search Keyword search across stored purpose summaries and file paths orstrum_list_files All indexed files, optionally filtered to one repo orstrum_analyze_impact Blast-radius analysis: walks the caller graph and reasons over affected files orstrum_get_guidance Routing guidance — when to use Orstrum vs. grep

Path resolution

All tools that accept a path parameter resolve it against the indexed file list. Four forms are accepted:

An absolute path: /home/user/project/src/api/auth.ts
A cwd-relative path: src/api/auth.ts
A repo/relPath shorthand (no extension): api-service/src/api/auth
A note form with .md: api-service/src/api/auth.md

There is no bare-basename form and no separate repo disambiguation parameter on the path-taking tools — the repo is part of the repo/relPath shorthand itself. (orstrum_search, orstrum_list_files, and orstrum_analyze_impact do take an optional repo filter, but that scopes results — it isn't a path disambiguator.)