Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CODEINTEL_DATA_DIRNoOverride default ~/.codeintel for all indexes and registry~/.codeintel
CODEINTEL_EMBEDDING_DOC_PREFIXNoOverride the document instruction prefix applied before embedding. Auto-detected for bge-m3, e5, and nomic-embed; set if using a different model that needs one.
CODEINTEL_EMBEDDING_QUERY_PREFIXNoOverride the query instruction prefix applied before embedding. Auto-detected for bge-m3, e5, and nomic-embed; set if using a different model that needs one.

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
documentSymbolsA

List every top-level symbol (with its range) defined in path within repo.

goToDefinitionA

Resolve symbol's definition location(s) within repo.

findReferencesB

Every occurrence of symbol within repo, definition sites included.

callHierarchyA

Single-level incoming/outgoing call hierarchy for symbol within repo.

typeHierarchyA

Single-level super/subtypes for symbol within repo.

Returns an explicit error when the index carries no relationship data —
`scip expt-convert` does not populate `global_symbols.relationships`, so
an empty result would wrongly imply the symbol has no supertypes.
getIndexStatusA

Whether repo has a published index, and its freshness. Pass repo_path (the repo's local git working directory) to compare the published commit against git rev-parse HEAD; omitted, freshness is reported without a staleness comparison.

searchCodeA

Lexical code search via an embedded Zoekt index (lazy-started on first call). repo, if given, is applied as a Zoekt r: query filter scoping results to that one indexed repo; omitted, results span every indexed repo.

semanticSearchA

Natural-language code search over repo: embeds query, retrieves top vector matches from the repo's semantic index, fuses them with Zoekt lexical hits via reciprocal rank fusion. Requires the repo to have been indexed with the semantic extra installed.

blastRadiusA

2-hop bounded BFS over the package dependency graph: every other indexed repo whose package directly (1 hop) or transitively through one intermediary (2 hops) depends on symbol_or_package as registered for repo (built by codeintel index, e.g. "npm:@scope/name"). The graph has no per-node timestamp, so freshness is always reported as unknown here — an honest limitation, not a bug.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 9 tools

Disambiguation5/5

Each tool targets a clearly distinct code intelligence operation: symbol listing, definition resolution, references, call/type hierarchies, index status, lexical search, semantic search, and dependency impact analysis. No two tools serve the same purpose.

Naming Consistency4/5

All names are camelCase and reasonably descriptive, but the pattern is not fully uniform: some start with verbs (goTo, find, get, search) while others are noun phrases (callHierarchy, typeHierarchy, blastRadius). This minor inconsistency does not seriously impede readability.

Tool Count5/5

Nine tools is well-scoped for a code intelligence server, covering standard queries without excess. Each tool contributes a distinct capability and none feel redundant.

Completeness5/5

The surface covers core code intelligence workflows: symbol navigation, references, hierarchies, search (both lexical and semantic), index freshness, and dependency blast radius. No obvious dead ends or missing critical operations for the implied scope.

Maintenance

ActivityMaintained
ResponsivenessResponsive