This server has significant definition quality gaps. While tool names follow verb_noun conventions well and schemas are present, parameter descriptions are sparse or missing entirely. Most tools lack descriptions of what they return and when to use them. The server demonstrates basic schema structure but lacks the documentation depth, error guidance, and composition clarity expected of production tools. Average per-tool score: 42/100.
Misleading tool name: 'mobile_list_apps' does not list apps. According to description, it checks if an app is installed. This violates pattern:tool naming clarity, name must convey action accurately.
22 tools lack documented output schemas. Agents cannot know what fields to expect in responses, forcing guesswork and failed downstream tool chaining. E.g., create_session should document that it returns a sessionArn; list_devices should document returned device structure.
Rename mobile_list_apps to mobile_check_app_installed (or mobile_is_app_installed) to accurately reflect its behavior of checking whether a single app is installed, not listing all apps.
Document output schemas for all 22 tools. For each, specify returned fields, types, and purpose. Example: 'create_session returns {sessionArn: string, remoteDeviceUrl: string, status: string}'.
Expand parameter descriptions to include format, constraints, and examples. Example: 'appId: Package identifier in format com.company.app (e.g., com.android.chrome). Required for launch/install/terminate operations.'
Document the coordinate system for mobile interaction tools (mobile_click_on_screen_at_coordinates, mobile_double_tap_on_screen, mobile_long_press_on_screen_at_coordinates): specify whether coordinates are in pixels or percentages, define origin (top-left or center?), and document valid ranges based on screen size returned by mobile_get_screen_size.
Add recovery guidance to error responses. When a tool fails, return actionable error messages. Example: 'Session pre-signed URL expired (retryable). Call refreshDriver() or create a new session with create_session.' Implement pattern:recovery-guide.
Add confirmation/dry-run patterns for destructive operations. For stop_session, mobile_terminate_app, and mobile_uninstall_app, require an explicit 'confirm=true' parameter or offer a dry_run mode that previews action without executing.
Clarify session management. Document whether each tool operates on a 'current' session (global state) or accepts a sessionId parameter. If global, document how to switch sessions. If per-parameter, refactor tools to accept sessionId explicitly instead of relying on global currentSessionArn.
Parameter descriptions are sparse or missing across all tools. Examples: appId (multiple tools) has no format guidance (is it 'com.example.app'?); coordinates (x, y) lack bounds documentation; percent in mobile_swipe_on_screen is unexplained. Agents cannot infer valid ranges or formats.
Destructive operations (stop_session, mobile_terminate_app, mobile_uninstall_app) lack confirmation patterns or dry-run options. Agents can destructively modify state without safeguards, violating pattern:confirmation-request.
Tool relationships are undocumented. E.g., create_session vs install_and_launch_app both manage app setup, unclear when to use which. list_active_sessions returns sessions but no guidance on extracting sessionArn for stop_session. mobile_install_app vs create_session's apkPath upload, what's the difference?
Coordinate system is not documented across mobile interaction tools. E.g., mobile_click_on_screen_at_coordinates uses (x, y) but does not specify: pixel or percentage? Origin (top-left? center?)? Bounds (0-device_width)? Agents will hallucinate invalid coordinate values.
No error handling guidance. Tools do not explain what errors are retryable, user-fixable, or fatal. E.g., if create_session fails with 'pre-signed URL expired' (code visible in refreshDriver()), the agent receives no recovery hint. Missing pattern:recovery-guide and pattern:error-classification.
Many tool descriptions are under 20 characters (rubric hard cap at 40 points). Examples: 'Get screen orientation' (23 chars), 'List all elements on screen' (27 chars), 'Get device information' (21 chars). These descriptions lack context for tool selection, agents cannot distinguish when to call mobile_get_orientation vs mobile_get_screen_size.
Global state ('currentSessionArn', 'DEVICE_FARM_URL', 'driver') is referenced in code but no tool documents how sessions are selected or isolated. When stop_session is called, which session does it stop? The 'current' one, but how is 'current' established? Violates stateless request handling principle.
No pagination support on list_devices or list_active_sessions. If a user has many devices or sessions, these tools will return all results, potentially flooding the context window. Missing pattern:paginated-result.
list_deviceslist_active_sessions
Add limit and offset/cursor parameters to list_devices and list_active_sessions. Example: 'list_devices(platform=ANDROID, limit=20, offset=0)' and return {devices: [...], total: 150, nextOffset: 20}. Implement pattern:paginated-result.
Document tool relationships. Add 'See also' sections or dependency notes. Example: In create_session description, add 'This creates a remote session. Use install_and_launch_app() to install and launch an app within the session, or mobile_launch_app() if already installed.'
Expand install_and_launch_app and create_session descriptions. Clarify whether apkPath in create_session auto-installs (doc says 'manual install required') vs mobile_install_app which explicitly installs. Remove ambiguity.
Document parameter relationships and constraints. Example: In mobile_swipe_on_screen, explain 'percent: 0-100, distance as percentage of screen dimension in the specified direction. Default is 50 if omitted.'
Add input validation constraints to tool descriptions. Example: 'path parameter must be an absolute file path; directory must exist and be writable.'
Expand descriptions to 50-200 characters (rubric baseline for A-grade tools). Current descriptions often too brief to guide tool selection. Example: Instead of 'Get device screen size', write 'Get the device screen dimensions in pixels. Returns {width, height}. Call this before calculating coordinates for mobile_click_on_screen_at_coordinates.'
Document which mobile_* tools require an active session vs which work without one. If mobile_get_device_info requires a running session, state it clearly.