codemap_stats
Get code graph statistics including total file count, symbol count, and dependency count. Quick project overview without full orient output.
Usage Examples
MCP Usage (for AI Agents like Claude)
json
{
"name": "codemap_stats",
"arguments": {}
}Example Output
JSON Response
json
{
"success": true,
"files": 299,
"directories": 47,
"symbols": 3099,
"dependencies": 173
}When to Use This Tool
-
Use
- Get quick project size metrics
- Check if code graph is populated
- Compare project complexity
- Track project growth over time
- Get counts without full orient output
codemap_stats when you need to:
Pro Tips
- Faster than orient: Stats-only call is quicker than full orientation
- Real-time counts: Reflects current code graph state
- No parameters needed: Zero-config tool call
- Dependencies = import relationships: Not npm packages, but code dependencies
- Symbols/file ratio: Good complexity metric (lower = simpler)
Best Practices
- Use for quick checks without verbose output
- Track stats over time to monitor project growth
- Compare stats across projects to assess complexity
Common Mistakes
â Mistake: Expecting npm package count
â Instead: Dependencies are code import relationships
â Mistake: Using when orient would be better
â Instead: Use orient for full context, stats for quick metrics only
â Instead: Dependencies are code import relationships
â Mistake: Using when orient would be better
â Instead: Use orient for full context, stats for quick metrics only