Skip to main content
Glama
nzrsky

xctools-mcp-server

xctrace_record

Record an Instruments trace using a specified template to analyze system performance and app behavior. Attach to processes or launch commands for targeted profiling.

Instructions

Record a new Instruments trace using the specified template.

Args: template: Template name or path to use for recording output_path: Path to save the trace file device: Device name or UDID to record on time_limit: Time limit for recording (e.g., '5s', '1m') all_processes: Record all processes on the system attach_process: Process name or PID to attach to launch_command: Command and arguments to launch and record

Returns: Recording result

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
templateYes
output_pathNo
deviceNo
time_limitNo
all_processesNo
attach_processNo
launch_commandNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations exist, and the description fails to disclose behavioral traits such as whether recording starts immediately, required permissions, or side effects. Only a minimal return type 'Recording result' is mentioned.

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 concise with a clear first sentence and a bullet list for parameters. Every sentence adds information without unnecessary text.

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 tool with 7 parameters and no annotations, the description covers basic parameter meanings but lacks information on output schema details, error cases, and usage context. Incomplete given the complexity.

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

Parameters4/5

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

With 0% schema description coverage, the description adds value by explaining each parameter (e.g., time_limit with examples). However, details like format constraints are missing for some parameters.

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 records an Instruments trace using a specified template. It distinguishes from sibling xctrace tools (export, import, list, symbolicate) by its unique action and resource.

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 on when to use this tool vs alternatives like xctrace_export or xctrace_list. No when-not or prerequisite information provided.

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/nzrsky/xctools-mcp-server'

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