AndroJack-mcp

Google Play Store Policy Advisor

android_play_policy_advisor

Read-onlyIdempotent

Check Google Play policy requirements before app submission or monetization, covering target API, minor access, subscriptions, permissions, data safety, and large-screen quality.

Instructions

Play policy reference: target API requirement, Restrict Minor Access, subscription transparency, restricted permissions and Data Safety, large-screen quality. Call before Play submission or new monetization.

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": "android_play_policy_advisor"
  }
}

Input Schema

Name	Required	Description	Default
`topic`	No	Topic: 'overview', 'subscriptions', 'restrict minor access', 'permissions', 'large screen quality'
`refresh`	No	Resend content already sent in this session

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.1.0Oct 18, 2026

addedInput schema / properties / refresh

Added value: +{
+  "description": "Resend content already sent in this session",
+  "type": "boolean"
+}

First observedv1.7.1Jun 11, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds that this is a reference/advice tool and that it should precede submission, but says nothing about what the advice contains or how the refresh flag changes session behavior beyond the schema field's own text.

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?

Two sentences, front-loaded with the resource and followed by the trigger condition. The topic list is somewhat long but each item maps to real coverage; nothing is padded.

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?

For a simple, zero-required-parameter, read-only reference tool with full schema coverage and complete annotations, the description supplies the needed purpose and timing. The only minor omission is any hint at output shape (e.g., checklist vs citations), which is not critical for an advisory tool.

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

Parameters3/5

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

Schema description coverage is 100%, so both the topic list and the refresh semantics are already documented in the schema. The description's topic enumeration largely restates the schema's topic examples without adding format or default-substitution guidance. Baseline 3 is appropriate.

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?

States a specific resource (Play Store policy reference) and enumerates the concrete domains it covers: target API requirement, Restrict Minor Access, subscription transparency, permissions/Data Safety, large-screen quality. An agent can tell this apart from generic siblings like android_component_status, though it does not explicitly distinguish itself from android_permission_advisor or android_api36_compliance, which overlap on permissions and API level.

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

Usage Guidelines4/5

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

Provides an explicit trigger: 'Call before Play submission or new monetization.' That is a clear when-to-use signal. It stops short of when-not to use it or naming the overlapping permission/API-compliance siblings as alternatives.

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