Skip to main content
Glama
Sign In
AndroJack-mcp

AndroJack-mcp

by VIKAS9793
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Android Official Documentation Search

android_official_search
Read-onlyIdempotent

Search official Android/Kotlin docs before writing code, returning source-linked excerpts or stating when no match exists.

Instructions

Call first, before writing Android/Kotlin code. Returns official developer.android.com / kotlinlang.org excerpts with source URLs (Google Developer Knowledge API when configured, else a verified page index). If nothing matches it says so — do not fall back to memory.

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": {
      "query": "<query>"
    },
    "name": "android_official_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query — be specific. E.g. 'Compose LazyColumn performance', 'WorkManager constraints'.
refreshNoResend content already sent in this session

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / refresh
      Added value: +{
+  "description": "Resend content already sent in this session",
+  "type": "boolean"
+}
  2. First observedv1.7.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered; the description goes beyond them by disclosing the dual data-source behaviour ('Google Developer Knowledge API when configured, else a verified page index') and the empty-result contract. It also describes return content (excerpts with source URLs), which matters because there is no output schema. No rate limits or latency expectations are given, but nothing contradicts 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?

Three short sentences, front-loaded with the imperative action, then the return contract, then the failure-mode guidance. No filler and nothing requiring rereading.

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 two-parameter read-only search with rich annotations, the description covers purpose, timing, return shape and empty-result handling, which is close to sufficient even without an output schema. It stops short of full completeness only by not positioning itself against the many topic-specific sibling guides.

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 (including the example queries for 'query' and the resend semantics for 'refresh'). The description adds no parameter-level detail beyond what the schema already carries, so the baseline of 3 applies.

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: it searches and returns official developer.android.com / kotlinlang.org excerpts with source URLs. It is clearly distinguishable from sibling reference tools (e.g. kotlin_best_practices, material3_expressive) because it is scoped as a general source-backed lookup rather than a curated guide, and it names its actual data sources.

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 an explicit triggering condition — 'Call first, before writing Android/Kotlin code' — plus an exclusion: if nothing matches, do not fall back to memory. What it does not do is say when to prefer the specialised sibling guides over this general search, so selection between this tool and the other ~20 Android tools is left partly to inference.

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

Deploy Server

Other Tools