AndroJack-mcp

Android Component Status Validator

android_component_status

Read-onlyIdempotent

Check if an Android/Kotlin class or library is stable, deprecated, or removed before using official APIs. Returns status, replacement, and doc link; unknown names are unconfirmed.

Instructions

Is an Android/Kotlin class or library stable, deprecated, or removed? Call before using any android., androidx. or kotlin.* API. Returns status, replacement, and doc link; unknown names are reported as unconfirmed, never guessed.

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

Input Schema

Name	Required	Description	Default
`component_name`	Yes	Full or short class name to validate. E.g. 'AsyncTask', 'android.widget.ProgressDialog', 'LiveData'.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.7.1Jun 11, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description adds genuinely useful behavior: it discloses the return contents (status, replacement, doc link) and, importantly, that unknown names are 'reported as unconfirmed, never guessed' — a non-obvious reliability guarantee beyond the annotations.

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

Conciseness5/5

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

Two tightly written sentences, front-loaded with the core question, followed by the call condition and return/edge-case behavior. Every clause earns its place with no filler.

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

Completeness5/5

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

With no output schema, the description correctly takes on the burden of describing what comes back (status, replacement, doc link) and how ambiguous inputs behave. For a single-input validation tool, nothing an agent needs to invoke it correctly is missing.

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% and the single parameter is documented with concrete examples ('AsyncTask', 'android.widget.ProgressDialog', 'LiveData'). The description adds no additional parameter semantics, so the baseline 3 is appropriate.

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 states a specific verb and resource — validating whether an Android/Kotlin class or library is stable, deprecated, or removed — and does so as a crisp question an agent can match against a need. It is clearly distinct from search/general-knowledge siblings like android_official_search because it returns a lifecycle verdict rather than documents.

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?

It gives explicit when-to-use guidance: 'Call before using any android.*, androidx.* or kotlin.* API.' That is a clear triggering condition. It does not name an alternative sibling or state exclusions, so it falls short of a 5.

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