LiLBrain
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Path to the project directory to index |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lilbrain_overviewA | Project overview: files, functions, classes, languages, subsystems, pipelines. Start here. |
| lilbrain_functionA | Look up any function by name. Returns signature, location, callers, callees, language. |
| lilbrain_callersB | Call graph for a function: who calls it and what it calls. |
| lilbrain_searchB | Search everything: functions, classes, sections, constants. |
| lilbrain_fileB | Get info about a file: functions, classes, sections, language. |
| lilbrain_readB | Read source code of a function (by name) or file region (by path + line range). |
| lilbrain_subsystemB | Deep dive into a subsystem: files, top functions, languages. |
| lilbrain_pipelineB | Trace a named pipeline or pattern (parse, validate, handle, compile, etc.). |
| lilbrain_dataflowB | Data flow: upstream callers and downstream callees for a function. |
| lilbrain_traceB | Depth-limited call chain trace from a function. |
| lilbrain_hotspotsB | Most connected functions (highest fan-in + fan-out). |
| lilbrain_architectureC | Architecture: subsystems, cross-subsystem dependencies, language mix. |
| lilbrain_impactA | Blast radius: if you change this function, what breaks? Affected callers, subsystems, risk level. |
| lilbrain_diagramB | Auto-generate Mermaid or D2 architecture diagrams. Target: "architecture", subsystem name, or function name. |
| lilbrain_deadcodeA | Find dead code: functions with zero callers, grouped by subsystem, with LOC waste estimate. |
| lilbrain_clonesA | Detect near-duplicate functions using token similarity. Finds copy-paste code. |
| lilbrain_complexityB | Cyclomatic + cognitive complexity analysis. Per-function detail or top-N ranking. |
| lilbrain_complexity_velocityB | Track complexity changes over recent git history. Shows which commits touched complex code. |
| lilbrain_semanticA | Semantic search: find functions by meaning, not just name. "handle authentication" finds verify_token, check_session, etc. |
| lilbrain_federationA | Multi-repo federated search: query across multiple codebases at once. |
| lilbrain_askA | Ask a natural language question about the codebase. Auto-routes to the right analysis tool. |
| lilbrain_diffA | Git-aware graph diff: changed functions, blast radius, risk level between any two refs. |
| lilbrain_pr_reviewB | Auto-generate PR review context: changes, blast radius, new cross-subsystem edges, complexity delta, risk. |
| lilbrain_runtimeB | Correlate OpenTelemetry/Jaeger traces with static call graph. Find hot production paths and cold code. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 24 tools
Several tools cover overlapping call-graph and impact territory: callers, dataflow, trace, impact, diff, and pr_review all involve upstream/downstream callers and blast radius. Overview, architecture, and subsystem also blur boundaries, while search, semantic, and ask offer vaguely differentiated discovery paths.
All tools share the lilbrain_ prefix and use snake_case, which gives a consistent visual pattern. However, naming mixes noun-style resources (function, callers, hotspots) with verb-style actions (read, search, ask), so the convention is not perfectly uniform.
24 tools is at the heavy end of the borderline range. The domain is broad enough to justify many specialized analyses, but the overlapping call-graph and discovery tools suggest the set could be consolidated without losing capability.
The toolset is remarkably complete for read-only code intelligence: it covers navigation, call graphs, dataflow, impact analysis, architecture, code quality, dead code, clone detection, semantic search, diffs, PR review, and runtime correlation. There are no obvious dead ends for typical codebase understanding workflows.