Idencify
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| symbol_searchB | Hybrid semantic + keyword search over all symbols in the indexed repository. |
| get_definitionA | Fetch the full source and metadata of a symbol by name or id. |
| get_contextB | Assemble task-relevant code context for a natural-language question. |
| analyze_impactC | List symbols and files affected by changing a given symbol (reverse dependencies). |
| expand_call_graphC | Walk callers/callees from a symbol up to a given depth. |
| detect_cyclesB | Find dependency cycles between symbols and files. |
| check_boundariesB | Verify architectural boundaries between modules and layers. |
| find_patternC | Locate structural code patterns across the repository. |
| summarize_fileA | Summarize a file's symbols, relations and role in the codebase. |
| health_scoreA | Score repository health: dead code, cycles, coupling, coverage of the graph. |
| graph_diffB | Diff the code graph between two points in time (added/removed symbols and edges). |
| semantic_changelogB | Human-readable changelog derived from graph changes between syncs. |
| search_historyB | Search past ingestion/sync history of the repository. |
| rate_contextA | Feedback loop: rate the usefulness of previously returned context. |
| sync_repositoryA | Trigger re-indexing of the connected repository. |
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 15 tools
Each tool targets a distinct aspect of code analysis—search, definition, context, impact, graph traversal, cycle detection, boundary checks, pattern finding, file summary, health score, graph diff, changelog, history, feedback, and sync. Even seemingly related tools like analyze_impact and expand_call_graph are clearly separated by their focus on reverse dependencies versus call graph walking.
The majority of tools follow a verb_noun pattern (get_definition, analyze_impact, detect_cycles), but several deviate—symbol_search, health_score, graph_diff, and semantic_changelog use reversed or noun-first conventions, weakening predictability across the set.
With 15 tools, the server is at the upper edge of the ideal range, yet each tool serves a distinct and necessary function for a comprehensive code intelligence platform, ensuring no tool feels redundant or extraneous.
The tool set covers a full lifecycle: ingesting/triggering syncs, searching and retrieving symbols, analyzing dependencies and cycles, enforcing architecture, finding patterns, summarizing files, assessing health, tracking changes over time, and even incorporating feedback—leaving no obvious gaps for its domain.