Key takeaways
- Group calls into sessions to turn noise into a funnel.
- The drop between stages tells you where to look.
- Overlay completed vs stopped paths to name the culprit tool.
Individual calls are noise until you group them into sessions. A session is one client's run from connect to outcome, and it behaves exactly like a funnel you would recognize from product analytics.
The stages
- Connected: the client established a session
- Reached a tool: it actually called something
- Completed a workflow: it got to a useful result
Where people fall out
The interesting number is the drop between stages. If most sessions connect but few reach a tool, your tool descriptions or discovery are the problem. If they reach a tool but rarely complete, the failure is downstream, often a single tool breaking a common path.
From funnel to fix
Overlay completed versus stopped paths and the culprit usually names itself: the same tool, at the same step, ending sessions. That is where a fix pays off most.
See this on your own server
TrackMCP turns your MCP server's calls into adoption, workflows, and outcomes. One line to install.