Google Play Console

get_crash_rate

Fetch user-perceived crash rates from Android Vitals to monitor app stability and avoid Play Store ranking penalties. Returns daily crash data filtered by version code.

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "package_name": "<package_name>"
    },
    "name": "get_crash_rate"
  }
}

Input Schema

Name	Required	Description	Default
`days`	No
`package_name`	Yes
`version_code`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.5.7May 6, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_crash_rateOutput",
-  "type": "object"
-}New value: +null

First observedv0.5.0Mar 24, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. Discloses data returned and a threshold, but lacks details on error handling, rate limits, or expected response format. Does not explicitly state read-only nature.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Reasonably concise with a clear flow: purpose, returns, threshold, then args. The args section could be integrated more concisely, but overall efficient.

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?

No output schema, but description explains return values and threshold. Lacks details on error conditions and data format, but sufficiently complete for a simple fetch tool.

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?

Schema description coverage is 0%, and the description compensates by explaining package_name (with example), days (default 7, max 30), and version_code (optional). This adds meaning beyond the raw schema.

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?

The description clearly states the tool fetches user-perceived crash rate from Android Vitals, listing specific return values (daily crashRate, userPerceivedCrashRate, distinctUsers) and a threshold. This distinctively separates it from siblings like get_anr_rate (ANR rate) and get_vitals_summary (summary).

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?

No explicit guidance on when to use this tool versus alternatives (e.g., get_anr_rate, get_vitals_summary). Does not state when not to use or provide context for selection.

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

Deploy Server