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

ios-instruments-mcp

by bfernandesbfs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

analyze_network

Record a network trace of an iOS app to detect slow requests, analyze transfer sizes, and receive optimization suggestions.

Instructions

Record a Network trace and report slow requests, transfer sizes, and optimization suggestions.

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_network"
  }
}

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

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must convey all behavioral traits. It mentions recording and reporting but omits side effects, permissions needed, or whether it modifies app state. For a recording tool, this is insufficient.

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 captures the core functionality. It is efficient and front-loaded, though slightly more structure could improve scanning.

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?

There is no output schema, so the description should explain the return format. It lists outputs but not structure. Also, the relationship to sibling tool analyze_network_trace is unclear, leaving gaps for the agent.

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%, so the schema adequately documents parameters. The description adds no additional context beyond the schema, meeting the baseline but not exceeding it.

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 a network trace and reports specific outputs (slow requests, transfer sizes, optimization suggestions). It distinguishes from sibling tools by focusing on network analysis, with specific deliverables.

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 alternatives like analyze_network_trace. The description implies usage for network performance but does not provide context or exclusions.

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