Skip to main content
Glama
mobile-next

Mobile Next MCP Server

Official
by mobile-next

List Crash Reports

mobile_list_crashes
Read-only

List crash reports available on a device to identify and analyze app failures.

Instructions

List crash reports available on the device

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deviceYesThe device identifier to use. Use mobile_list_available_devices to find which devices are available to you.

Implementation Reference

  • Handler function for mobile_list_crashes tool. Calls mobilecli.crashesList(device) and returns the result as JSON.
    	async ({ device }) => {
    		ensureMobilecliAvailable();
    		const response = mobilecli.crashesList(device);
    		return JSON.stringify(response.data);
    	}
    );
  • src/server.ts:810-823 (registration)
    Tool registration using the local `tool()` helper function which wraps server.registerTool().
    tool(
    	"mobile_list_crashes",
    	"List Crash Reports",
    	"List crash reports available on the device",
    	{
    		device: z.string().describe("The device identifier to use. Use mobile_list_available_devices to find which devices are available to you."),
    	},
    	{ readOnlyHint: true },
    	async ({ device }) => {
    		ensureMobilecliAvailable();
    		const response = mobilecli.crashesList(device);
    		return JSON.stringify(response.data);
    	}
    );
  • Input schema: requires a 'device' string parameter.
    {
    	device: z.string().describe("The device identifier to use. Use mobile_list_available_devices to find which devices are available to you."),
    },
    { readOnlyHint: true },
  • Helper on the Mobilecli class that executes 'mobilecli device crashes list --device <id>' and parses the JSON response.
    crashesList(deviceId: string): MobilecliCrashesListResponse {
    	const output = this.executeCommand(["device", "crashes", "list", "--device", deviceId]);
    	return JSON.parse(output) as MobilecliCrashesListResponse;
    }
  • Type definitions for the crash list response.
    export interface MobilecliCrashEntry {
    	processName: string;
    	timestamp: string;
    	id: string;
    }
    
    export interface MobilecliCrashesListResponse {
    	status: "ok";
    	data: MobilecliCrashEntry[];
    }
Behavior2/5

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

The description adds no behavioral context beyond the annotation 'readOnlyHint: true'. It does not disclose side effects, error conditions (e.g., no crashes found), or return format. Given the annotation already indicates read-only behavior, the description fails to add further value.

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 a single sentence that efficiently communicates the core purpose without unnecessary words. It is front-loaded with the key action and resource.

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?

The description is too minimal. It does not specify the return value (e.g., list of crash identifiers or metadata), nor does it mention edge cases (e.g., no crashes, device offline). With no output schema, the description should provide more context about what the agent can expect.

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%, and the schema description for 'device' is thorough, referencing another tool for discovery. The tool description does not add additional parameter context, so it meets the baseline for high schema coverage.

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 action ('List') and the resource ('crash reports available on the device'). It distinguishes from the sibling tool 'mobile_get_crash', which retrieves a specific crash report, by indicating this tool lists all available reports.

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 is provided on when to use this tool versus alternatives like 'mobile_get_crash'. The description does not mention prerequisites, such as first using 'mobile_list_available_devices' to get device IDs, even though the input schema references it.

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/mobile-next/mobile-mcp'

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