Skip to main content
Glama
VIKAS9793

AndroJack-mcp

by VIKAS9793
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Kotlin Multiplatform (KMP) Guide

android_kmp_guide
Read-onlyIdempotent

Fetch Kotlin Multiplatform setup, libraries, Room, Ktor, expect/actual, and Gradle guidance to build Android apps with current KMP references.

Instructions

Kotlin Multiplatform reference: project setup, KMP libraries (Ktor not Retrofit, Koin not Hilt in commonMain), Room KMP and Room 3, expect/actual. Topics: overview, libraries, room, ktor, expect actual, gradle.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicNoTopic: 'overview', 'libraries', 'room', 'ktor', 'expect actual', 'gradle'
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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds only the topical scope; it says nothing about how content is chunked or returned, and the session-dedup behavior is disclosed in the schema (refresh), not here.

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?

A single compact passage with the core purpose front-loaded and the topic list trailing as supporting detail. The trailing list is mildly redundant with the schema but does not bloat the text.

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 tool with no output schema and full schema coverage on both params, the description covers what the tool is and what it spans. Only the shape of the returned guidance is unspecified, a minor gap given the annotations carry the safety profile.

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 coverage is 100% and both parameters are fully documented in the schema, so the baseline is 3. The description merely repeats the topic list already present in the schema and adds no syntax, formatting, or default-value nuance for 'refresh'.

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?

The description names a specific resource (Kotlin Multiplatform reference) and enumerates its scope: project setup, KMP libraries, Room KMP/Room 3, expect/actual. It implicitly distinguishes itself from generic siblings like kotlin_best_practices by scoping to KMP, but never names an alternative explicitly.

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

Usage Guidelines3/5

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

The topic list implies when the tool is relevant, but there is no explicit 'use this when...' guidance, no exclusions, and no routing advice against siblings such as android_official_search or kotlin_best_practices. Usage must be inferred from the topic enumeration.

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