Benchmarking Mobile Agent Planning Capabilities
Listen to the summary
Uses a voice available on your device
Audio options
On this page 4 sections
Related concepts 2 concepts
Key Takeaways
- The top-performing model, Claude-Opus-5, reached an overall weighted score of 75.52%.
- Current frontier LLMs are unreliable for autonomous mobile tasks, showing a minimum failure rate of 24.48%.
- Memory usage is a significant bottleneck, with model performance ranging between 33.78% and 64.63%.
- Agents frequently hallucinate tool calls when facing capability limits or execution errors rather than using feedback to adapt.
Summary & Methodology Analysis
The researchers developed MobilePA-Bench to provide an interactive, stateful, and tool-centric environment for evaluating agent performance in mobile scenarios. Unlike existing frameworks like AndroidWorld or OSWorld, which focus on Vision-Language Models (VLMs) that inspect screenshots and predict pixel-level coordinates, this benchmark maps mobile operations into executable function signatures. This approach builds upon the paradigm used in general-domain benchmarks like the Berkeley Function Calling Leaderboard and ToolBench, while incorporating specific mobile requirements seen in datasets like DroidCall and AppBench. The evaluation framework supports multi-turn user interactions, mirroring transactional workflows similar to those found in TAU-Bench.
Baseline evaluations across 13 models reveal that performance remains far from the requirements for reliable autonomous deployment. The strongest agent, Claude-Opus-5, achieves an overall weighted score of 75.52%. A persistent challenge across these models is memory management, where performance averages only 50.98%, with scores as low as 33.78% and as high as 64.63%. The platform also evaluates how agents combine basic actions into executable code abstractions, utilizing concepts similar to those in VOYAGER or SkillBench, and examines task scheduling akin to environments like OpenCLAW.
The research identifies a critical reliability gap, as even the most capable agents exhibit a failure rate of at least 24.48%. A major contributor to this is the inability of models to handle runtime exceptions, such as PermissionDenied errors. When models encounter capability limits, ambiguous constraints, or execution exceptions, they tend to issue premature, hallucinated tool calls rather than asking for clarification or adjusting their strategies based on feedback. This indicates that current frontier models lack the robust planning logic needed for dynamic mobile environments.
Interactive System Flowchart
Cross-Examination & FAQs
A deeper dive clarifying mechanics, constraints, and baseline evaluations.
Q1. What is MobilePA-Bench?
It is an interactive, stateful, and tool-centric benchmark for evaluating the planning and tool-calling abilities of mobile planning agents.
Q2. How well do current agents perform?
The top-performing model, Claude-Opus-5, achieves an overall weighted score of 75.52%.
Q3. Why are current mobile agents considered unreliable?
Even the best-performing models show a failure rate of at least 24.48%, indicating they are not yet ready for autonomous deployment in dynamic mobile environments.
Q4. How does this benchmark compare to OSWorld or AndroidWorld?
While OSWorld and AndroidWorld focus on Vision-Language Models that use pixel-level coordinates from screenshots, MobilePA-Bench focuses on tool-centric planning via executable function signatures.
Q5. What is the primary cause of agent failure when encountering errors?
Models tend to issue premature, hallucinated tool calls rather than using feedback to recover or asking for clarification when they face capability limits or execution exceptions like PermissionDenied.
Q6. How do models perform regarding memory usage?
Memory performance is a significant challenge, with a 13-model mean of 50.98% and a range between 33.78% and 64.63%.
Q7. Does this benchmark evaluate multi-turn interactions?
Yes, it incorporates multi-turn user interaction to mimic transactional workflows, similar to the approach used in TAU-Bench.
Q8. What role do code abstractions play in the benchmark?
The benchmark evaluates the ability of agents to combine basic actions into executable, multi-step code abstractions, similar to the evaluations performed by frameworks like VOYAGER and SkillBench.
Q9. How are task operations mapped in this environment?
Similar to DroidCall and AppBench, the benchmark maps phone operations into executable function signatures.