Skip to main content
Glama
conorluddy

XC-MCP: XCode CLI wrapper

by conorluddy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List Crash Reports

idb-crash-list
Read-onlyIdempotent

List crash reports on an iOS simulator. Filter by bundle ID and timestamp to determine whether your app crashed or a tap simply failed, turning ambiguous interactions into actionable answers.

Instructions

idb-crash-list

List crash reports on a simulator, so an agent can tell a crash from a no-op.

Overview

Without this, a failed interaction is ambiguous: an agent cannot distinguish "my tap did nothing" from "the app crashed and is gone". Crash reports are written by the OS and persist across app launches and reboots.

Simulators accumulate crashes from unrelated system processes. An unfiltered list is mostly noise from other apps and extensions. The useful question is scoped: "did MY bundle crash since I launched it?" — so pass bundleId and since.

Parameters

Optional

  • udid (string): Target identifier - auto-detects if omitted

  • bundleId (string): Only crashes for this bundle (e.g. "com.example.MyApp")

  • since (number): Unix timestamp in SECONDS - only crashes newer than this

  • before (number): Unix timestamp in SECONDS - only crashes older than this

  • limit (number, default 20): Maximum crashes to return, newest first

Returns

crashCount, a crashes array (name, bundleId, processName, timestamp, occurredAt) and the filters that were applied. Pass a name to idb-crash-show for the full report.

Examples

Did my app crash during this test run?

const launchedAt = Math.floor(Date.now() / 1000);
// ... drive the app ...
await idbCrashListTool({ bundleId: 'com.example.MyApp', since: launchedAt });

Everything recent, regardless of app

await idbCrashListTool({ since: Math.floor(Date.now() / 1000) - 3600 });

Related Tools

  • idb-crash-show: Full report for one crash

  • idb-crash-delete: Remove reports (e.g. to get a clean baseline before a test)

  • simctl-stream-logs: Live log stream, which catches non-fatal errors a crash report will not

  • hang-start: Main-thread hangs, which produce no crash report at all

Notes

  • Timestamps are unix SECONDS, not milliseconds.

  • An empty list is a meaningful result: the app did not crash.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
udidNo
limitNoMax crashes to return, newest first (default 20)
sinceNoUnix timestamp in SECONDS - crashes newer than this
beforeNoUnix timestamp in SECONDS - crashes older than this
bundleIdNoOnly crashes for this bundle id

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
crashesYes
successYes
crashCountYesCrashes returned after applying limit
totalMatchedYesCrashes matching the filters before limit

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.1.0

TDQS

A5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the bar is lower, but the description adds valuable behavioral context beyond those hints: crash reports persist across launches/reboots, simulators accumulate unrelated system crashes, unfiltered lists are mostly noise, and an empty list is a meaningful non-crash result. No contradictions with annotations.

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 long but every section earns its place: Overview, Parameters, Returns, Examples, Related Tools, and Notes. It is front-loaded with the core purpose and scoping guidance, and examples are compact and directly illustrative.

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

Completeness5/5

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

Given the 5-parameter optional surface, existing output schema, and rich sibling set, this description is fully sufficient. It explains return shape, filter semantics, time units, common pitfalls, and how to route to related tools. An agent can correctly select and invoke this tool without additional inference.

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

Parameters5/5

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

Schema coverage is 80%, but the description goes well beyond the schema by clarifying udid auto-detection, emphasizing Unix SECONDS for timestamps, explaining the default limit, and providing concrete example values like 'com.example.MyApp'. The 'Returns' section also explains how filters map to results, which the schema does not convey.

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 opens with a specific verb+resource: 'List crash reports on a simulator,' and immediately frames the operational purpose ('so an agent can tell a crash from a no-op'). It also distinguishes itself from related tools like idb-crash-show and idb-crash-delete, making sibling differentiation explicit.

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

Usage Guidelines5/5

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

The description gives explicit when-to-use context: it resolves ambiguity between 'tap did nothing' and 'app crashed'. It also provides exclusions and alternatives, noting that simctl-stream-logs catches non-fatal errors and hang-start catches hangs that produce no crash report. It even prescribes the scoped pattern: pass bundleId and since.

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