unity-profiler-mcp

Overview Schema Source Related Servers Discussions Admin

profiler_compare

Compare two groups of Unity Profiler captures marker by marker to report group means, run-to-run spread, and flag performance differences larger than that spread.

Instructions

Compare two groups of captures (e.g. 3 runs of branch A vs 3 of branch B) per marker. Reports group means, the run-to-run spread inside each group, and flags differences larger than that spread.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "a": "<a>",
      "b": "<b>"
    },
    "name": "profiler_compare"
  }
}

Input Schema

Name	Required	Description
`a`	Yes	Captures of group A.
`b`	Yes	Captures of group B.
`limit`	No
`folder`	No	Capture folder. Default: UNITY_PROFILER_CAPTURES or <project>/ProfilerCaptures from the open editor.
`sortBy`	No
`contains`	No
`maxDepth`	No	Only markers at or above this hierarchy depth (0 = PlayerLoop level).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 3, 2026

TDQS

A3.5/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden and does usefully disclose that it reports group means, within-group spread, and flags differences larger than that spread. It does not clarify read-only behavior, prerequisites, failure modes, performance characteristics, or whether any side effects occur.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no wasted wording. It communicates purpose and expected output efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter tool with no output schema and no annotations, the description covers the high-level purpose and output summary but leaves important gaps around parameter effects, return structure, and operational behavior. It is adequate for initial selection but not fully complete for confident invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 57%, and the description explains only the group arrays conceptually. It does not add meaning for limit, sortBy, contains, or maxDepth, and only partially covers folder behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: compare two groups of captures per marker, including group means and spread. It does not explicitly name or distinguish the sibling tools, but the operation is clearly distinct from listing, summarizing, exporting, and top-marker tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The example of comparing 3 runs of branch A vs 3 runs of branch B provides clear usage context. There are no explicit exclusions or named alternatives, but the intended scenario is easy to infer.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server