tracy_status
Probe whether native Tracy profiling is usable on the running game by testing TCP connectivity and CLI availability, returning a status with error hints for troubleshooting.
Instructions
Probe whether native-Tracy profiling is usable on the running game.
RUN THIS FIRST. The capture path used by this server is the game's
embedded native Tracy server (TCP 8086), driven by the bundled
tracy-capture / tracy-csvexport CLIs. It does NOT use the Python
_utility.getCpuFrameData binding (absent on most release builds) and
does NOT go through MCDK. Reports:
native_tracy.reachable— can we open a TCP connection to 8086? (the tracy-profiler GUI connects to the same port)bin_present— are the bundled Tracy CLIs available?mcdk— MCDK MCP endpoint, informational only (just tracy_jank_fps needs it; native capture is independent). Best-effort.
ok is true when the native path is ready (reachable + bin present);
otherwise reason/hint pinpoint the broken leg.
Args: address/port: native Tracy endpoint (default 127.0.0.1:8086). project_dir: optional path whose .mcdev.json gives MCDK's MCP port.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| port | No | ||
| address | No | 127.0.0.1 | |
| project_dir | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||