Skip to main content
Glama

get_crash_rate

Fetch user-perceived crash rate data from Android Vitals to monitor app stability, identify versions exceeding Play Store thresholds, and prevent ranking penalties by analyzing daily metrics.

Instructions

Fetch user-perceived crash rate from Android Vitals.

Returns daily crashRate, userPerceivedCrashRate, and distinctUsers by version code. Bad behavior threshold: userPerceivedCrashRate > 1.09% may cause Play Store ranking penalties.

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_crash_rate tool, which fetches crash rate data from Android Vitals via the _reporting() utility and formats the result.
    @mcp.tool()
    def get_crash_rate(
        package_name: str,
        days: int = 7,
        version_code: str = "",
    ) -> str:
        """Fetch user-perceived crash rate from Android Vitals.
    
        Returns daily crashRate, userPerceivedCrashRate, and distinctUsers by
        version code. Bad behavior threshold: userPerceivedCrashRate > 1.09%
        may cause Play Store ranking penalties.
    
        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_crash_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 crash data available. Data may lag up to 2 days "
                            "or the app has no crashes in this period."
                        ),
                        "rows": [],
                    },
                    indent=2,
                )
            return json.dumps(
                {
                    "packageName": package_name,
                    "periodDays": days,
                    "badBehaviorThreshold": {"userPerceivedCrashRate": 0.0109},
                    "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?

With no annotations, description carries full burden and discloses output fields (crashRate, userPerceivedCrashRate), temporal granularity ('daily'), and domain-specific risk thresholds. Missing: auth requirements, rate limits, or caching behavior.

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?

Front-loaded with purpose in first sentence. Efficient structure separating return value documentation, threshold warning, and Args section. Every sentence adds value; zero redundancy.

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

Completeness4/5

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

Excellent coverage given output schema exists (no need to detail return structure). Includes specific business logic thresholds (1.09%) essential for App Store health monitoring. Minor gap: no mention of authentication requirements or error cases for invalid package names.

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 has 0% description coverage; description fully compensates with semantic meaning for all 3 parameters: provides package_name format example ('com.example.myapp'), days constraints ('max 30'), and clarifies version_code as an optional filter.

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?

Opens with specific verb ('Fetch') + resource ('user-perceived crash rate') + source ('Android Vitals'). Clearly distinguishes from sibling vitals tools like get_anr_rate and get_wakelock_rate by specifying crash metrics.

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 valuable interpretation guidance (1.09% threshold for Play Store penalties) indicating when results are concerning, but lacks explicit differentiation from siblings like get_vitals_summary or get_anr_rate for metric selection.

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