Skip to main content
Glama

get_wakelock_rate

Monitor background wakelock rates in Android apps to identify excessive battery usage and avoid Play Store penalties by analyzing stuck wakelock data from Android Vitals.

Instructions

Fetch stuck background wake lock rate from Android Vitals.

Returns daily stuckBackgroundWakelockRate and distinctUsers by version code. Excessive wakelock holding (>1 hour in background) may be penalized.

Args: package_name: Package name, e.g. com.example.myapp days: Past days to include (default 7, max 30). version_code: Optional version code filter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
package_nameYes
daysNo
version_codeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The implementation of the get_wakelock_rate tool handler, which queries Android Vitals via _reporting().query_wakelock_rate and formats the output.
    def get_wakelock_rate(
        package_name: str,
        days: int = 7,
        version_code: str = "",
    ) -> str:
        """Fetch stuck background wake lock rate from Android Vitals.
    
        Returns daily stuckBackgroundWakelockRate and distinctUsers by version
        code. Excessive wakelock holding (>1 hour in background) may be penalized.
    
        Args:
            package_name: Package name, e.g. com.example.myapp
            days: Past days to include (default 7, max 30).
            version_code: Optional version code filter.
        """
        days = max(1, min(days, 30))
        try:
            raw = _reporting().query_wakelock_rate(
                package_name=package_name,
                days=days,
                version_code=version_code or None,
            )
            rows = _parse_reporting_rows(raw.get("rows", []))
            if not rows:
                return json.dumps(
                    {
                        "packageName": package_name,
                        "message": (
                            "No stuck wakelock data available. Data may lag up to 2 days "
                            "or the app has no wakelock violations in this period."
                        ),
                        "rows": [],
                    },
                    indent=2,
                )
            return json.dumps(
                {
                    "packageName": package_name,
                    "periodDays": days,
                    "totalRows": len(rows),
                    "rows": rows,
                },
                indent=2,
            )
        except Exception as exc:
            return json.dumps({"success": False, "error": str(exc)}, indent=2)
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses return values (stuckBackgroundWakelockRate, distinctUsers), daily granularity, and business consequences (penalization). However, lacks explicit read-only safety declaration, rate limits, or auth requirements that would fully compensate for missing annotations.

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?

Excellent structure with purpose front-loaded in first sentence, return value explanation second, penalty context third, followed by Args section. Every sentence earns its place with no redundancy.

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

Completeness5/5

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

Sufficient for a read-only metrics tool. Mentions key return fields despite existence of output schema, documents all parameters, and explains metric significance. No critical gaps given the tool's complexity and available structured fields.

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

Parameters5/5

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

Schema description coverage is 0%, requiring full compensation. The Args section documents all 3 parameters with semantics: package_name includes example (com.example.myapp), days includes default (7) and constraint (max 30), version_code notes optionality. Fully compensates for empty schema descriptions.

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

Purpose5/5

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

States specific action 'Fetch', specific metric 'stuck background wake lock rate', and source 'Android Vitals'. Clearly distinguishes from siblings like get_anr_rate, get_crash_rate, and get_wakeup_rate by specifying the exact vital sign being queried.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides context about what the metric measures (excessive wakelock holding >1 hour may be penalized), implying when to monitor this, but lacks explicit when-to-use guidance versus alternatives like get_vitals_summary or get_wakeup_rate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AgiMaulana/GooglePlayConsoleMcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server