Skip to main content
Glama
Sign In
ios-instruments-mcp

ios-instruments-mcp

by bfernandesbfs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

analyze_time_profiler_trace

Analyze a Time Profiler trace file (.xctrace) to identify CPU hotspots and performance bottlenecks in an iOS app.

Instructions

Analyze an existing .xctrace file recorded with the Time Profiler template.

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": {
      "trace_path": "<trace_path>"
    },
    "name": "analyze_time_profiler_trace"
  }
}

Input Schema

NameRequiredDescriptionDefault
trace_pathYesAbsolute path to the .xctrace file.
bundle_idNocom.unknown.app

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as side effects, required permissions, or return value characteristics. For an analysis tool, it is unclear if it is read-only or what it produces.

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 a single concise sentence that conveys the purpose without excess. However, it could be slightly expanded to include parameter hints or use-case context.

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?

Given no output schema, the description should explain what the analysis result entails (e.g., summary of CPU usage). It only states 'analyze', leaving the agent without expectation of return values or next steps.

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 50% (only 'trace_path' has a schema description). The tool description adds no information about parameters, so it fails to compensate for the missing schema description of 'bundle_id'.

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 analyzes an existing .xctrace file recorded with the Time Profiler template, specifying the verb, resource, and condition. This distinguishes it from sibling tools like 'analyze_time_profiler', which likely starts a new profiling session.

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 explicit guidance is provided on when to use this tool versus alternatives like 'analyze_time_profiler'. The description implies use for existing trace files, but lacks explicit when-not or alternative recommendations.

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

Deploy Server

Other Tools