AndroJack-mcp

Android Architecture Reference

architecture_reference

Read-onlyIdempotent

Retrieve official Android architecture guidance for a topic before proposing app structure; use 'list' to see all supported topics.

Instructions

Official Android architecture guide for a topic (mvvm, compose, navigation, hilt, viewmodel, room, workmanager, paging, datastore, coroutines, flow, testing, lifecycle, modularization, security…). Call before proposing app structure. Pass 'list' for all topics.

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

Input Schema

Name	Required	Description	Default
`topic`	Yes	Architecture topic. E.g. 'mvvm', 'compose', 'hilt', 'modular architecture'. Pass 'list' for all topics.
`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.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds meaningful behavioral context the annotations do not: that the content is an official curated guide, that it should be fetched proactively before structural decisions, and that a 'list' sentinel enumerates topics. It omits that content is session-cached and re-sent only via the refresh flag, which lives only in the schema.

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?

Three short sentences, front-loaded with the purpose, then the usage imperative, then the discovery sentinel. The parenthetical topic enumeration is long but arguably earns its place by defining the accepted vocabulary.

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 read-only reference lookup with no output schema, the agent knows what to pass and roughly what it gets back (a topic guide). It would be stronger with a sentence on return shape (e.g. markdown guide text vs. code samples) or how to chain results into further design work.

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% – both 'topic' and 'refresh' carry their own descriptions including the 'list' sentinel and session-cache semantics. The description largely restates the schema's topic examples, adding no syntax or format information beyond it, so the baseline 3 applies.

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 verb and resource: it retrieves an official Android architecture guide for a named topic, and it enumerates the valid topic space. It does not, however, distinguish itself from overlapping siblings such as android_navigation3_guide, android_testing_guide, or kotlin_best_practices, whose topical coverage intersects with the listed topics.

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?

"Call before proposing app structure" gives a clear triggering context for the agent, and "Pass 'list' for all topics" gives a concrete discovery path. There is no when-not guidance and no routing advice for the overlapping sibling guides, so it stops 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.