MCP server for verified APK downloads from RuStore by package name
Two tools with complete schemas and detailed descriptions. Naming follows verb_noun convention (get_apk_info, download_apk). Descriptions are comprehensive (150-280 chars) and explain WHAT, WHEN, and prerequisites. Tool annotations present (readOnlyHint, destructiveHint). However, parameter descriptions are minimal, 'exact Android package name, e.g. com.yolo_price_mobile' repeats across both tools without explaining constraints. max_mib parameter lacks range validation guidance in description (should state '1..4096, default 1024' in param description, not just tool description). Output schemas are not documented, callers cannot see what fields to expect from invoke() results. Error handling is generic (ToolError wrapper) without recovery guidance.
Download the latest free standalone APK from RuStore using just its package name. Returns absolute local path, version, byte size, SHA-256, certificate and cached flag. Verifies the package/version in AndroidManifest and APK signature against RuStore. Reuses a verified cached copy of the same version. max_mib: 1..4096, default 1024. Requires Android SDK aapt/apksigner and Java on the server host. May take several minutes. Does not install or run the APK. Call sequentially for a package list; stop on HTTP 403/429.
Get latest RuStore release metadata by exact Android package name, e.g. com.yolo_price_mobile. Returns name, version, minimum Android SDK, price and source. Does not download any APK. A listing does not guarantee that a standalone APK is available.
Output schemas not documented. Tool descriptions state what is returned (name, version, size, SHA-256, certificate, cached flag) but no formal schema is visible in code. LLMs cannot plan downstream operations without knowing field names and types.
Parameter descriptions lack constraint details. max_mib description in tool docstring says '1..4096, default 1024' but the parameter annotation itself has no description field, only the tool description mentions the range. LLMs cannot validate input without explicit param-level constraints.
Error handling is generic. ToolError wraps exceptions but provides no recovery guidance. E.g., 'HTTP 403/429' mentioned in description but not handled with actionable error messages like 'Rate limited. Wait before retrying.' or 'Unauthorized. Check RuStore credentials.'
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 56 | 2025-06-18+ | v2 |
Repeated parameter description across tools. Both tools describe package_name identically ('exact Android package name, e.g. com.yolo_price_mobile'). Example values in descriptions risk LLM literal reuse; should use enum or pattern constraint instead.
No idempotency guidance. download_apk mentions 'Reuses a verified cached copy' but does not explicitly state whether repeated calls with same package_name are safe. Agents need to know if retries risk duplicate downloads or side effects.