io.github.partprogramming09/metal-gpu-trace

5 of 16 tools are described as changing something (creating, editing, deleting, sending or running).

• perf_recordruns code or commandsdescribed as changing data

  “Records `program` (an .exe under Wine, or a macOS binary with wine="native"), or a test program fetched with workload_fetch (workload, api, dim), for `seconds` with Metal System Trace and returns its…”

  Publisher declares: read-only no · destructive yes · idempotent no · open-world no

  10 inputs, 1 required

  • labelstringrequired“name for the run: letters, digits, '.', '_', '-'”
  • programstring“path of the .exe, or of the macOS binary with wine=native”
  • secondsinteger“recording length, default 20; use 30 under Wine, whose start-up takes part of it; the export afterwards takes about a minute”
  • winestring“Wine directory holding bin/wine, or native”
  • prefixstring“Wine prefix, default WINEPREFIX or ~/.wine; ignored with native”
  • workdirstring“directory the program starts in, default the program's own”
  • argsstring“program arguments as in a shell, quotes included”
  • workloadstring“a test program from workload_list, fetched with workload_fetch, instead of program”
  • apistring“with workload: mtl (native Metal), d3d11 or d3d12 (under wine)”
  • diminteger“with workload drawstress: side of the cube grid, dim^3 draws per frame”
• perf_baseline_recordruns code or commandsdescribed as changing data

  “Records the same program `count` times in a row with perf_record's arguments and saves the runs as the reference `name` for perf_check, returning the range each number spans across them.”

  Publisher declares: read-only no · destructive yes · idempotent no · open-world no

  11 inputs, 1 required

  • namestringrequired“reference name: letters, digits, '.', '_', '-'”
  • countinteger“equal recordings to make, default 3”
  • programstring“path of the .exe, or of the macOS binary with wine=native”
  • secondsinteger“recording length, default 20; use 30 under Wine, whose start-up takes part of it; the export afterwards takes about a minute”
  • winestring“Wine directory holding bin/wine, or native”
  • prefixstring“Wine prefix, default WINEPREFIX or ~/.wine; ignored with native”
  • workdirstring“directory the program starts in, default the program's own”
  • argsstring“program arguments as in a shell, quotes included”
  • workloadstring“a test program from workload_list, fetched with workload_fetch, instead of program”
  • apistring“with workload: mtl (native Metal), d3d11 or d3d12 (under wine)”
  • diminteger“with workload drawstress: side of the cube grid, dim^3 draws per frame”
• perf_attachruns code or commandsdescribed as changing data

  “Records a program that is already running, by pid or by a name in its command line (Game.exe under Wine), for `seconds` and returns the same summary as perf_record; the program keeps running.”

  Publisher declares: read-only no · destructive no · idempotent no · open-world no

  3 inputs, 2 required

  • labelstringrequired“name for the run: letters, digits, '.', '_', '-'”
  • processstringrequired“pid, or a name in the program's command line such as Game.exe”
  • secondsinteger“recording length, default 20; the export afterwards takes about a minute”
• perf_runsreads or searches

  “Lists the saved recordings, newest first, with frames, FPS, GPU ms per frame, memory peaks and the translation layer each ran on (fingerprint and Wine, or native).”

  Publisher declares: read-only yes · open-world no

  2 inputs

  • offsetinteger“first row, default 0”
  • limitinteger“rows per page, default 50, at most 500”
• perf_comparereads or searches

  “Compares two saved recordings (names from perf_runs), a the reference and b the run after a change: the headline numbers (FPS, GPU ms, frame pacing, memory), then what changed in the GPU work and whe…”

  Publisher declares: read-only yes · open-world no

  3 inputs, 2 required

  • astringrequired“run name from perf_runs: the reference, such as the run before a change”
  • bstringrequired“run name from perf_runs: the run to compare against a”
  • short_usinteger“an encoder under this GPU time counts as short: 10, 25 (default), 50, 100, 250, 500 or 1000”
• perf_baselinecreates or changes datadescribed as changing data

  “Names a reference for perf_check, or lists them.”

  Publisher declares: read-only no · destructive no · idempotent yes · open-world no

  2 inputs

  • namestring“reference name: letters, digits, '.', '_', '-'; alone, shows that reference”
  • runsarray“run names from perf_runs to save as this reference, ideally 3 or more equal runs; replaces a previous one”
• perf_checkreads or searches

  “Judges a recording against a reference saved with perf_baseline: regressed when FPS falls under the reference's lowest FPS by more than margin_pct, GPU ms per frame rises over its highest by more tha…”

  Publisher declares: read-only yes · open-world no

  3 inputs, 2 required

  • runstringrequired“a run name from perf_runs”
  • baselinestringrequired“a reference name from perf_baseline”
  • margin_pctnumber“how far outside the reference's range FPS or GPU ms per frame may fall before counting, default 3”
• perf_diagnosereads or searches

  “Says whether a saved recording splits its GPU work into too many short encoders, the pattern of translation layers such as DXMT, Mullion or MoltenVK, with the numbers behind it: encoders and command …”

  Publisher declares: read-only yes · open-world no

  4 inputs, 1 required

  • runstringrequired“a run name from perf_runs”
  • min_encodersinteger“encoders per frame (median) from which the verdict can be yes, default 4”
  • short_usinteger“an encoder under this GPU time counts as short: 10, 25 (default), 50, 100, 250, 500 or 1000”
  • short_sharenumber“share of short encoders from which the verdict is yes, default 0.25”
• trace_tablesreads or searches

  “Lists the data tables (schemas) a .trace recording holds; recordings keep their .trace only with KEEP_TRACE=1.”

  Publisher declares: read-only yes · open-world no

  1 input, 1 required

  • tracestringrequired“a run name from perf_runs whose trace_kept is true, or the path of a .trace”
• trace_countreads or searches

  “Counts the rows of several tables of a kept .trace, in all and per process, so a recording's useful tables show before reading them: a table with 0 rows needs another instrument or Xcode, not a bigge…”

  Publisher declares: read-only yes · open-world no

  2 inputs, 1 required

  • tracestringrequired“a run name from perf_runs whose trace_kept is true, or the path of a .trace”
  • tablesarray“table names from trace_tables; default the tables that matter for a translation layer”
• trace_queryreads or searches

  “Returns one page of rows of one table of a .trace as {column: value}, optionally only one process's rows.”

  Publisher declares: read-only yes · open-world no

  5 inputs, 2 required

  • tracestringrequired“a run name from perf_runs whose trace_kept is true, or the path of a .trace”
  • schemastringrequired“a table name that trace_tables lists, such as metal-gpu-intervals”
  • pidinteger“keep only this process's rows”
  • offsetinteger“first row, default 0”
  • limitinteger“rows per page, default 50, at most 500”
• capture_summaryreads or searches

  “Reads a Metal .gputrace capture without Xcode: command buffers, encoders, draws, debug groups, and the 100 most frequent call ids out of calls_total.”

  Publisher declares: read-only yes · open-world no

  1 input, 1 required

  • capturestringrequired“path of a .gputrace bundle saved from Xcode, inside METAL_TRACE_OUT or METAL_TRACE_READ”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.