Understand app capabilities as agent-accessible operations.
1. Platform role
AppFunctions lets authorized callers discover and invoke app capabilities through Android’s registry. The Android MCP analogy explains the tool surface; it does not mean a function is automatically a remote MCP server.
2. Availability
The documented platform support starts with Android 16, and the API remains an experimental preview. Production assistant integrations may have separate access restrictions. Verify current support before promising universal availability.
3. Function selection
Expose a narrow useful workflow such as searching tasks. Avoid mirroring every internal method or giving callers a general-purpose database query function.
Worked scenario
A task app exposes searchTasks with bounded filters rather than executeSql. The useful capability stays stable while internal storage can change.
Apply it
List five app workflows and select two with clear inputs, outputs and user value.
Check your understanding
You can explain both the capability and the current rollout limitations. Explain the decision and show evidence from your implementation or design. If you cannot demonstrate it yet, revisit the relevant section before continuing.