Skip to main content
Glama
Sign In
google-play-developer-mcp

google-play-developer-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

reports_anr_rate_get

Retrieve ANR rate metric-set metadata for your app to monitor stability and pinpoint performance issues.

Instructions

Get ANR-rate metric-set metadata.

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": {
      "name": "<name>"
    },
    "name": "reports_anr_rate_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.4/5.0
Behavior2/5

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

No annotations provided, so the description carries full burden. It only states 'Get' without disclosing behavioral traits like read-only nature, error handling (e.g., behavior if name not found), or rate limits. Minimal transparency.

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

Conciseness3/5

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

The description is a single concise sentence, but it is under-specified given the missing parameter context. It could benefit from a structured format (e.g., parameter description) without added fluff.

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

Completeness2/5

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

No output schema or annotations exist, and the description fails to explain return values, prerequisites (e.g., valid metric set names), or how to interpret the response. The tool is incomplete for an agent to use correctly without prior knowledge.

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

Parameters1/5

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

Schema description coverage is 0%, and the description adds no explanation for the 'name' parameter. It does not clarify what the name refers to (e.g., metric set name), leaving the agent to guess. No enums or examples provided.

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 states the verb 'Get' and resource 'ANR-rate metric-set metadata', distinguishing it from query siblings like reports_anr_rate_query which likely fetch actual data. While not a tautology, it could be more specific about what 'metadata' includes.

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 guidance on when to use this tool versus alternatives such as reports_anr_rate_query or reports_crash_rate_get. No context on prerequisites or typical workflow.

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