AndroJack-mcp

Android Error Debugger

android_debugger

Read-onlyIdempotent

Parse Android/Kotlin stacktraces to identify the error class, then return matching official documentation and an Issue Tracker search link for faster debugging.

Instructions

Parse an Android/Kotlin stacktrace and return the error class, matching official docs, and an Issue Tracker search link. Paste the exception line and 'at' frames.

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": {
      "stacktrace": "<stacktrace>"
    },
    "name": "android_debugger"
  }
}

Input Schema

Name	Required	Description	Default
`refresh`	No	Resend content already sent in this session
`stacktrace`	Yes	Full Android/Kotlin stacktrace or exception text. Include the exception class and 'at' frames.

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.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description adds genuinely useful behavior beyond the structured fields: it discloses that the tool performs doc-matching and constructs an Issue Tracker search link, which is real output behavior given no output schema exists.

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?

Two tight sentences with zero filler. The purpose and outputs come first, followed by the one actionable input instruction, so nothing needs to be re-read.

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 parse tool with full schema coverage and no output schema, the description is nearly sufficient: it explains what is returned and what input to supply. It stops short of covering limits (the 4000-char cap is only in the schema) or what happens on an unparseable stacktrace, but the core need is met.

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%, so both parameters are already documented in the schema, including the refresh flag the description never mentions. The description's restatement of the stacktrace content ('include the exception class and at frames') duplicates the schema text rather than adding format or syntax guidance, so 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 ('Parse an Android/Kotlin stacktrace') and enumerates the outputs (error class, matching official docs, Issue Tracker link), so the agent knows exactly what the tool produces. It does not, however, reference or distinguish itself from the large set of sibling guide/search tools, so differentiation is left implicit.

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?

Usage is only implied: 'Paste the exception line and "at" frames' tells the agent the input format but not the situations that select this tool over alternatives like android_official_search. There are no exclusions or named alternatives, so the agent must infer when to reach for it.

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