GliderTrace tools are grouped by runtime evidence workflow. This page lists what each tool is for and links to the exact per-tool API reference.
Use the exact tool names in agent prompts when you want the MCP client to collect, inspect, or export stored runtime evidence.
trace_statustrace_runtrace_run_testsdotnet test and stores test evidence, TRX artifacts, stdout, stderr, and summarized failures.trace_starttrace_stoptrace_start, terminates the launched process, and finalizes stored evidence.trace_import_otlptrace_import_artifactstrace_list_processestrace_attachtrace_capture_dumptrace_capture_gcdumptrace_get_sessiontrace_query_eventstrace_compare_sessionstrace_exporttrace_correlate_codetrace_exceptionstrace_counterscounters.csv evidence for a session.trace_hotspotsdotnet commands.trace_export for compact CI or agent summaries when raw artifacts are too large or sensitive for prompt context.