Skip to main content
Glama
Sign In
Ultimate Android MCP

Ultimate Android MCP

by oddlyspaced
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_top_activities

Identify the current foreground activity on a connected Android device. Returns the top activity without requiring parameters, enabling UI context checks and automation.

Instructions

Returns the activities currently on top on the connected Android device. No parameters are required.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_top_activities"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It communicates that the tool reads current device state by saying it 'returns' activities, but it does not disclose the return format, possible failure modes, or how 'on top' is defined. This is minimally adequate for a simple query tool but lacks richer behavioral detail.

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 front-loaded sentence that states the core behavior and then confirms the lack of required parameters. There is no filler, redundancy, or unnecessary detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a parameterless, read-only tool, the description is mostly sufficient, but because there is no output schema it does not clarify whether the plural 'activities' implies a list, a stack, or a single value. It also does not address the ambiguity with the sibling get_top_activity, leaving some context incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters and the schema coverage is 100%, so there is little for the description to add. It explicitly states 'No parameters are required,' which reinforces the empty schema and meets the baseline for a parameterless tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the action ('Returns') and the resource ('activities currently on top on the connected Android device'). It is unambiguous about what the tool reports, but it does not differentiate itself from the closely named sibling 'get_top_activity', so it misses the top score.

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?

There is no guidance on when to use this tool instead of alternatives such as get_top_activity or other UI inspection tools. The only usage-related note is that no parameters are required, which is already evident from the empty schema.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools