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

ios-instruments-mcp

by bfernandesbfs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

analyze_time_profiler

Record a Time Profiler trace to report hot methods that consume the most CPU time in an iOS app.

Instructions

Record a Time Profiler trace and report hot methods consuming the most CPU time.

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": {
      "bundle_id": "<bundle_id>",
      "device_id": "<device_id>"
    },
    "name": "analyze_time_profiler"
  }
}

Input Schema

NameRequiredDescriptionDefault
bundle_idYesApp bundle ID, e.g. com.mycompany.myapp
device_idYesSimulator UUID or physical device ID. Use list_devices to find it.
time_limit_secondsNoRecording duration in seconds (default 20s).

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 provided, so the description must cover behavioral traits. It mentions recording implying a write operation but does not disclose side effects (e.g., trace persistence, permissions) or resource usage. Agents need more transparency for safe invocation.

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?

Single sentence of 16 words efficiently conveys core purpose. However, it sacrifices useful guidance that could be added without significant bloat.

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?

Lacks context on return value format (no output schema), no guidance on usage context, and insufficient behavioral transparency. For a tool with three parameters, the description is incomplete for an agent to fully understand its usage.

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 coverage is 100% with clear descriptions for all three parameters. The description adds no extra parameter information beyond the schema, so baseline score of 3 is appropriate.

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 clearly states the action 'Record a Time Profiler trace' and the output 'report hot methods'. It implies a new recording, distinguishing it from the sibling 'analyze_time_profiler_trace' which likely works on existing traces. However, it could be more explicit about sibling differentiation.

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 versus siblings like analyze_allocations or analyze_leaks. The description is generic and lacks decision criteria for agents to choose this tool appropriately.

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