Skip to main content
Glama

profiler

Read-only

Start, stop, and analyze Unity profiling sessions to capture frame timing, memory snapshots, CPU usage, render stats, and GC allocations. Save and review performance data to identify bottlenecks.

Instructions

Controls Unity's Profiler for performance analysis. Actions:

  • start: Begin profiling session

  • stop: End profiling session

  • get_frame_data: Get detailed frame timing data

  • get_memory_snapshot: Capture memory usage snapshot

  • get_render_stats: Get rendering statistics (draw calls, triangles, batches)

  • get_cpu_usage: Get CPU time breakdown by area

  • get_gc_allocs: Get garbage collection allocations

  • save_report: Save profiler data to file

  • clear: Clear profiler data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesProfiler action to perform
sortByNoSort profiler results by this metric
minTimeNoMinimum time in ms to include in results (filter small items)
savePathNoFile path for saving profiler report
frameCountNoNumber of frames to analyze (default: 1, max: 300)
profileGPUNoInclude GPU profiling data
deepProfileNoEnable deep profiling for detailed call stacks (slower)
profileEditorNoInclude editor overhead in profiling
memoryCategoriesNoMemory categories to include in snapshot
includeCallStacksNoInclude call stacks in GC allocation data
Behavior1/5

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

The description includes mutating actions (start, stop, clear) yet the annotation declares readOnlyHint: true, which is a contradiction. The description does not disclose side effects or behavioral traits beyond the annotation's implication.

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

Conciseness4/5

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

The description is concise and front-loaded with the purpose and a list of actions. It avoids unnecessary words but could benefit from grouping related actions.

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

Completeness2/5

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

With 10 parameters and no output schema, the description is insufficient. It does not explain return values, default behaviors, or how parameters interact with different actions.

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

Parameters3/5

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

Schema description coverage is 100%, so the description adds minimal additional meaning. It does not elaborate on parameter usage or relationships beyond what the schema provides.

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

Purpose5/5

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

The description clearly states the tool controls Unity's Profiler for performance analysis, and lists specific actions (start, stop, get_frame_data, etc.), making the tool's purpose distinct from siblings like profile_xr_scene.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives (e.g., profile_xr_scene for XR-specific profiling). There is no mention of prerequisites or context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/joel-wehr/unity-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server