Skip to main content
Glama
VIKAS9793

AndroJack-mcp

by VIKAS9793
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Gradle Dependency Version Checker

gradle_dependency_checker
Read-onlyIdempotent

Fetches current stable versions and ready-to-paste Gradle Kotlin DSL/TOML for Android, Kotlin, or Jetpack libraries, including BOM handling, before adding or bumping dependencies.

Instructions

Current stable version and ready-to-paste Gradle (Kotlin DSL / TOML) for an Android, Kotlin, or Jetpack library from Google Maven / Maven Central, including BOM handling. Accepts a name ('room', 'compose-bom', 'coil') or exact 'group:artifact'. Call before adding or bumping any dependency.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refreshNoResend content already sent in this session
library_nameYesLibrary name. E.g. 'compose', 'room', 'hilt', 'retrofit', 'kotlin-stdlib', 'coil', 'paging'.

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.4/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, openWorld, and non-destructive behavior. The description adds useful output behavior, specifying stable version plus Gradle DSL/TOML snippets and BOM handling, though it does not describe error cases or refresh semantics beyond 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.

Conciseness5/5

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

Three compact sentences front-load the output, then input form, then when to call. No repetition or filler; every clause adds operational detail.

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?

With no output schema, the description does the key work by naming the return content and Gradle formats. It leaves minor edge cases such as unknown library handling unstated, but it is sufficient for an agent to decide when and how to call it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds meaningful syntax guidance: it accepts a short name or exact 'group:artifact'. The 'refresh' parameter is left to the schema, but its description there is adequate.

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 exactly what it returns: current stable version and ready-to-paste Gradle for Android/Kotlin/Jetpack from Google Maven/Maven Central, including BOM handling. It also states accepted input forms, so an agent can distinguish it from general Android search/reference tools.

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?

Provides a clear pre-call trigger: 'Call before adding or bumping any dependency.' It also clarifies accepted input shorthand, but does not state limitations such as unsupported repositories or whether it works for non-Android libraries.

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