Axon Pro
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 | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| axon_pro_list_reposA | List all indexed repositories with their stats. |
| axon_pro_queryB | Search the knowledge graph using hybrid (keyword + vector) search. Returns ranked symbols matching the query. |
| axon_pro_contextA | Get a 360-degree view of a symbol: callers, callees, type references, and community membership. |
| axon_pro_impactC | Blast radius analysis: find all symbols affected by changing a given symbol. |
| axon_pro_dead_codeB | List all detected dead code in the repository. |
| axon_pro_detect_changesB | Analyse code changes in a diff and find affected symbols. Helps understand the impact of recent modifications. |
| axon_pro_cypherC | Execute a raw Cypher query against the knowledge graph. |
| axon_pro_file_contextC | Get full context for a specific file, including all its symbols. |
| axon_pro_related_filesB | Find files that are structurally or temporally coupled to a given file. |
| axon_pro_flow_traceC | Trace the execution flow downstream starting from a specific symbol to understand its behavior deeply. |
| axon_pro_architectureB | Get a high-level architectural overview of the project (Models, Controllers, Jobs, etc). |
| axon_pro_search_codeC | Search for code patterns or literal snippets across the indexed content. |
| axon_pro_explain_flowB | Explain the execution flow of a symbol in natural language, categorizing downstream actions. |
| axon_pro_check_nplus1B | Scan for potential N+1 query patterns or heavy database usage in the indexed code. |
| axon_pro_impact_on_testsB | Identify which tests might be affected by changing a specific symbol. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Codebase Overview | High-level statistics about the indexed codebase. |
| Dead Code Report | List of all symbols flagged as unreachable. |
| Graph Schema | Description of the Axon Pro knowledge graph schema. |
| AI Agent Guidelines | Instructions for AI agents on how to use Axon Pro effectively. |
TDQS
Scored across 15 tools
Most tools target distinct analyses, but several pairs overlap: flow_trace vs explain_flow both trace downstream execution of a symbol (only output format differs), impact vs impact_on_tests overlap, and query vs search_code could be confused. Descriptions help but an agent may still misselect between the flow-tracing and impact variants.
All tools use a predictable axon_pro_ prefix with consistent snake_case, and most names are verb_noun or clear noun phrases. Minor inconsistency between pure verbs (query, context, cypher) and noun-based names, but overall readable and uniform.
15 tools sit at the top of the ideal range and each targets a specific code-intelligence capability. The set is well-scoped for a knowledge-graph code analysis server with no obvious filler.
The surface covers repository listing, semantic and literal search, symbol/file context, impact analysis, dead code, diff analysis, raw graph queries, architecture, flow tracing, and test impact. This is a thorough lifecycle for code-intelligence work with no glaring gaps.