AndroJack-mcp

Android Developer Verification Program

android_developer_verification

Read-onlyIdempotent

Determine if you're affected by Android developer verification. Get official details on registration paths, enforcement timelines, and enterprise exemptions.

Instructions

Android developer verification (identity check; enforced since Sept 30, 2026 in BR/ID/SG/TH, global 2027): who is affected, registration paths, enterprise exemptions. Topics: overview, timeline, registration, enterprise, studio.

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_developer_verification"
  }
}

Input Schema

Name	Required	Description	Default
`topic`	No	Topic: 'overview', 'timeline', 'registration', 'enterprise', 'studio'
`refresh`	No	Resend content already sent in this session

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.1.0Oct 18, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare a safe, read-only, idempotent, non-open-world lookup, so the safety profile is covered. The description adds useful domain context (identity-check program, enforcement window, exempted categories), but says nothing about what a call returns (content chunks vs. summary), caching, or how 'refresh' behaves beyond the schema line.

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?

One tight, front-loaded sentence plus a short topic list; no filler and the identifying information comes first. The parenthetical dates and regions are dense but relevant and earn their place.

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

Completeness3/5

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

There is no output schema, so the description carries the burden of explaining the return, and it does not (no format, granularity, or size indication). For a policy-information tool with all-optional parameters and full annotation coverage, this is adequate but leaves the agent guessing about the shape of the result.

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 coverage is 100% and both parameters are documented there, so the baseline is 3. The description's topic list simply restates the schema's topic values and adds no extra meaning about semantics, defaults, or behavior when topic is omitted.

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 names a specific resource (the Android Developer Verification program) and enumerates the sub-topics it can answer ('who is affected, registration paths, enterprise exemptions'). An agent can tell it is a documentation/knowledge tool about a specific policy program. It stops short of naming a sibling it is distinct from, so it is not a 5.

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?

Usage is only implied: the topic list hints at what this tool is good for, but there is no explicit when-to-use or when-not, and no routing against closely related siblings such as android_play_policy_advisor or android_official_search. The agent must infer the boundary itself.

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