api-flow-analyzer

Tools are mostly distinct: track_call handles input, while analyze_flow, detect_redundancy, get_dependency_graph, and suggest_batching each target a different analytical output. The broad analyze_flow overlaps slightly with the more specific analysis tools, but descriptions make the intended use clear enough.

All tool names follow a consistent verb_noun pattern with clear action verbs like analyze, calculate, detect, get, suggest, and track. The naming style is uniform and predictable across the entire set.

Six tools cover the full analysis workflow without bloat or redundancy. The count is well-scoped for an API flow analyzer, and each tool has a clear role.

The tool set covers recording calls, analyzing flows, detecting redundancy, building dependency graphs, suggesting batching, and calculating savings. Minor gaps exist around managing or listing recorded flows, but the core analysis lifecycle is well represented.