Code Intelligence (MCI)
Semantic understanding of your codebase — not just search, but architectural context.
Why MCI exists: Grep finds strings. MCI finds meaning.
When you ask "what calls this function?" or "what would break if I change this file?",
MCI answers from the codebase's semantic graph — not just file contents.
Tool Reference
momental_code_search
Natural-language semantic search across the entire indexed codebase.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | required | Natural language query. E.g. "where is webhook authentication handled?" |
repoId | string | optional | Limit to a specific repo. Defaults to the team's primary repo. |
limit | number | optional | Max results. Default: 10. |
momental_code_symbol
Find all callers, implementations, and type signatures for a named symbol.
| Parameter | Type | Required | Description |
|---|---|---|---|
symbolName | string | required | Function, class, or variable name to look up. |
momental_code_file
Read a file with semantic annotations — co-change history, architectural context, and linked knowledge atoms.
momental_code_traces
Execution traces for a symbol — what happens end-to-end when this code runs.
momental_code_tests
Find all tests for a given file. Best source of verified, working usage examples.
momental_code_diff_impact
Given a list of changed file paths, returns all knowledge graph nodes affected — the blast radius of a PR.
| Parameter | Type | Required | Description |
|---|---|---|---|
filePaths | string[] | required | List of changed file paths relative to repo root. |
repoId | string | optional | Repo to analyse. Defaults to team's primary repo. |
momental_code_tour
Guided walkthrough of a feature area — key concepts, entry points, and architectural decisions.