AndroJack-mcp

Android Navigation 3 Guide

android_navigation3_guide

Read-onlyIdempotent

Retrieve official Navigation 3 reference before generating Android navigation code to prevent outdated Navigation 2 patterns; includes migration, scenes, backstack, testing, and key topics.

Instructions

Navigation 3 reference (current official library). Call before any navigation code — do not generate Navigation 2 NavController/NavHost for new projects. Topics: overview, migration, scenes, testing, backstack, key.

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

Input Schema

Name	Required	Description	Default
`topic`	No	Navigation topic: 'overview', 'migration', 'scenes', 'testing', 'backstack', 'key'
`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

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds genuine behavioral context beyond that: an ordering constraint (invoke before writing code) and a versioning rule (N3 is current, don't emit N2 code). It does not describe the shape of returned content, which keeps it short of a 5.

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?

Three short clauses, front-loaded with the resource identity followed by the action constraint, then the topic index. No filler sentences and nothing that could be trimmed without losing meaning.

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 zero-required-parameter read tool with no output schema and full schema coverage, the description covers purpose, timing, and available topics adequately. It could note what the returned content looks like (e.g., reference docs vs. code samples), but nothing essential 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 both parameters are documented there, so the baseline is 3. The description's topic list duplicates the schema's topic enumeration and adds no syntax or selection guidance beyond it.

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?

States a specific resource ('Navigation 3 reference') with an explicit version scoping cue ('current official library'), which cleanly distinguishes it from Navigation 2 material and from siblings like android_official_search. An agent immediately knows this returns N3 reference content.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('Call before any navigation code') and an explicit prohibition ('do not generate Navigation 2 NavController/NavHost for new projects'), which is stronger guidance than most sibling tools provide. Alternatives aren't named, but the when/when-not conditions are unambiguous.

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