Loading ToolBench
MCP server for exploring AOSP internals and Jetpack libraries
Android Source Explorer MCP provides 10 read-only tools for exploring Android Framework and AndroidX source code. While tool names follow verb conventions and input schemas are visible with type definitions, descriptions lack depth and specificity. Most descriptions are under 100 characters and do not explain WHEN to use each tool or provide recovery guidance. Parameter descriptions exist but are minimal. Output schemas are not documented, responses appear to be free-form strings or lists without typed field declarations. Error messages are generic (e.g., 'Class not found') and do not guide the agent toward recovery. The tool composition is reasonable (distinct concerns), but several tools are underspecified for production agent use. STDIO transport caps protocol readiness at 50.
Check the integrity of the local source cache and index.
Find all references to a symbol at a specific position (Requires LSP).
Get the inheritance hierarchy (superclass and interfaces) for a class.
Resolve the definition of a symbol at a specific position (Requires LSP).
List available versions for an AndroidX artifact (e.g. 'androidx.compose.runtime:runtime').
List all method and field signatures for a given class.
Retrieve the full source code for a given Android Framework or AndroidX class.
No documented output schemas. All tools return either string or list[string] without typed field definitions. LLMs cannot plan downstream calls or extract structured data.
Error messages are generic and do not guide recovery. Examples: 'Class not found. Try searching with search_classes.' appears only in lookup_class; others just return bare error strings. No actionable recovery hints.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 59 | 2026-07-28+ | v2 |
Look up a specific method's source code within a class.
Search for classes by glob pattern or substring (e.g. '*ViewModel*' or 'Activity').
Search for a text/regex pattern within a specific class or across all synced files (if class_name is omitted).
Descriptions lack context about WHEN to use each tool and why it differs from similar tools. E.g., search_in_source vs search_classes distinction is unclear in descriptions. Agents cannot disambiguate without reading source.
goto_definition and find_references claim to require LSP but no documentation explains prerequisites, setup, or failure modes. If LSP is not configured, these tools will fail silently or with cryptic errors.
check_integrity tool has no description explaining what 'integrity' means, what it checks, or what the output contains. Agents cannot decide whether to call it.
lookup_class accepts max_lines parameter but response indicates truncation with ellipsis. No structured way to request next chunk or paginate results.
search_classes and search_in_source both accept 'limit' parameter but response is unstructured. No 'total_results' count, 'has_more' flag, or 'next_cursor' to enable proper pagination.
Parameter 'pattern' in search_classes describes glob vs substring behavior but does not document which is preferred or give examples of valid patterns.