trace_import_artifacts

[external]

Imports existing workspace or artifact-root TRX, log, counters, nettrace, dump, or GC dump files into a GliderTrace session.

Why this tool exists

Important runtime evidence often already exists in files or in live local .NET processes.

How it helps the agent

The model can import artifacts or attach to a process while keeping evidence bounded and tied to a stored session.

Try it locally in the GliderTrace playground

Parameters

NameTypeRequiredDescription
sourcePathsjsonYesArtifact file paths under the workspace root or artifact root.
sourceKindstringNoOptional source kind: 'auto', 'trx', 'log', 'stdout', 'stderr', 'counters', 'nettrace', 'dump', or 'gcdump'. Defaults to auto.
captureSourceArtifactsbooleanNoCopy source files into the new session as sensitive artifact references. Defaults to true.
acknowledgeSensitivebooleanNoMust be true because this operation may read or store sensitive runtime artifacts.
maxEventsnumberNoMaximum normalized evidence events to import. Clamped to 1..5000. Defaults to 1000.

Examples

Import TRX evidence

Request
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "trace_import_artifacts",
    "arguments": {
      "sourcePaths": [
        "TestResults/results.trx"
      ],
      "sourceKind": "trx"
    }
  }
}

Response Notes

Returns an imported session with artifact references, parsed evidence counts, warnings, and failure summaries.

↑/↓ NavigateEnter OpenSpace Expand