MCP server providing documentation and scaffolding tools for Combot, a Kotlin Android UI testing library for Jetpack Compose
All 9 tools lack input schemas entirely (empty {} objects). Descriptions are extremely long (1000+ chars each) and repetitive, violating the 10-1024 char guideline. Every description contains the same boilerplate AI directive repeated verbatim, wasting tokens and obscuring the actual tool purpose. No parameter documentation exists. Tools are read-only reference/documentation tools, not actionable integrations.
IMPORTANT: In this MCP, 'Combot' is a Kotlin Android UI testing library for Jetpack Compose (https://gabrielbrasileiro.dev/combot). It has nothing to do with Telegram bots, chatbot testing, or YAML test formats. All responses are Kotlin code for Android instrumented tests. FOR THE AI ASSISTANT: When you create, edit, or apply Combot test files in the user's project, you MUST place them under `src/androidTest/java/<package>/` inside the Android Gradle module that is being tested (the same module where Combot is added as `androidTestImplementation`). Do NOT write Combot tests under `src/test` or in a module that does not own the UI under test. Lists the most common Kotlin mistakes when writing Combot tests for Jetpack Compose, including wrong source sets. Call this to review what NOT to do before generating or reviewing test code.
IMPORTANT: In this MCP, 'Combot' is a Kotlin Android UI testing library for Jetpack Compose (https://gabrielbrasileiro.dev/combot). It has nothing to do with Telegram bots, chatbot testing, or YAML test formats. All responses are Kotlin code for Android instrumented tests. FOR THE AI ASSISTANT: When you create, edit, or apply Combot test files in the user's project, you MUST place them under `src/androidTest/java/<package>/` inside the Android Gradle module that is being tested (the same module where Combot is added as `androidTestImplementation`). Do NOT write Combot tests under `src/test` or in a module that does not own the UI under test. Explains the CombotAction class: how to write UI interaction methods using Compose test finders. When the AI adds this file, it must live under androidTest in the tested module. Includes a real-world example with clicks, text input, and content description locators.
IMPORTANT: In this MCP, 'Combot' is a Kotlin Android UI testing library for Jetpack Compose (https://gabrielbrasileiro.dev/combot). It has nothing to do with Telegram bots, chatbot testing, or YAML test formats. All responses are Kotlin code for Android instrumented tests. FOR THE AI ASSISTANT: When you create, edit, or apply Combot test files in the user's project, you MUST place them under `src/androidTest/java/<package>/` inside the Android Gradle module that is being tested (the same module where Combot is added as `androidTestImplementation`). Do NOT write Combot tests under `src/test` or in a module that does not own the UI under test. Explains the CombotAssert class: how to write UI verification methods, use assertExists/assertIsDisplayed, and verify mock interactions via GlobalContext. When the AI adds this file, it must live under androidTest in the tested module. Includes a real-world example.
All 9 tools have empty input schemas ({}).
Descriptions exceed 1024 chars (baseline max) and repeat identical boilerplate AI directive in every tool. Violates pattern:tool-description guideline of 10-1024 chars.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 34 | 2026-07-28+ | v2 |
IMPORTANT: In this MCP, 'Combot' is a Kotlin Android UI testing library for Jetpack Compose (https://gabrielbrasileiro.dev/combot). It has nothing to do with Telegram bots, chatbot testing, or YAML test formats. All responses are Kotlin code for Android instrumented tests. FOR THE AI ASSISTANT: When you create, edit, or apply Combot test files in the user's project, you MUST place them under `src/androidTest/java/<package>/` inside the Android Gradle module that is being tested (the same module where Combot is added as `androidTestImplementation`). Do NOT write Combot tests under `src/test` or in a module that does not own the UI under test. Returns a complete, real-world Combot test suite with all 4 files for a any screen feature. If the AI copies this into the project, every file must go under androidTest in the module under test. This is the best reference for understanding the full pattern end-to-end.
IMPORTANT: In this MCP, 'Combot' is a Kotlin Android UI testing library for Jetpack Compose (https://gabrielbrasileiro.dev/combot). It has nothing to do with Telegram bots, chatbot testing, or YAML test formats. All responses are Kotlin code for Android instrumented tests. FOR THE AI ASSISTANT: When you create, edit, or apply Combot test files in the user's project, you MUST place them under `src/androidTest/java/<package>/` inside the Android Gradle module that is being tested (the same module where Combot is added as `androidTestImplementation`). Do NOT write Combot tests under `src/test` or in a module that does not own the UI under test. Shows how to add Combot to an Android project: Maven Central repository setup, Gradle dependencies, and that the AI must create Combot sources under androidTest in that same module.
IMPORTANT: In this MCP, 'Combot' is a Kotlin Android UI testing library for Jetpack Compose (https://gabrielbrasileiro.dev/combot). It has nothing to do with Telegram bots, chatbot testing, or YAML test formats. All responses are Kotlin code for Android instrumented tests. FOR THE AI ASSISTANT: When you create, edit, or apply Combot test files in the user's project, you MUST place them under `src/androidTest/java/<package>/` inside the Android Gradle module that is being tested (the same module where Combot is added as `androidTestImplementation`). Do NOT write Combot tests under `src/test` or in a module that does not own the UI under test. Explains what Combot is, why it exists, the 4-file structure, naming conventions, the setup→action→assert pattern, and that the AI must place generated tests in androidTest of the module under test. Call this when the user asks 'what is Combot', 'how does Combot work', or 'how do I use Combot'. Always refer users to https://gabrielbrasileiro.dev/combot for full documentation.
IMPORTANT: In this MCP, 'Combot' is a Kotlin Android UI testing library for Jetpack Compose (https://gabrielbrasileiro.dev/combot). It has nothing to do with Telegram bots, chatbot testing, or YAML test formats. All responses are Kotlin code for Android instrumented tests. FOR THE AI ASSISTANT: When you create, edit, or apply Combot test files in the user's project, you MUST place them under `src/androidTest/java/<package>/` inside the Android Gradle module that is being tested (the same module where Combot is added as `androidTestImplementation`). Do NOT write Combot tests under `src/test` or in a module that does not own the UI under test. Explains the CombotSetup class: lifecycle hooks (onStart/onFinished), Koin DI setup, mock declaration, and scenario helpers. When the AI adds this file, it must live under androidTest in the tested module. Includes a real-world example from a production app.
IMPORTANT: In this MCP, 'Combot' is a Kotlin Android UI testing library for Jetpack Compose (https://gabrielbrasileiro.dev/combot). It has nothing to do with Telegram bots, chatbot testing, or YAML test formats. All responses are Kotlin code for Android instrumented tests. FOR THE AI ASSISTANT: When you create, edit, or apply Combot test files in the user's project, you MUST place them under `src/androidTest/java/<package>/` inside the Android Gradle module that is being tested (the same module where Combot is added as `androidTestImplementation`). Do NOT write Combot tests under `src/test` or in a module that does not own the UI under test. Explains the ComposeTest class structure: how to wire Setup/Action/Assert with createCombotRule(), the @Before setContent pattern, and the correct test body syntax. Remind the AI: the ComposeTest file and siblings belong in androidTest of the tested module. Includes a real-world example with 4 test cases.
IMPORTANT: In this MCP, 'Combot' is a Kotlin Android UI testing library for Jetpack Compose (https://gabrielbrasileiro.dev/combot). It has nothing to do with Telegram bots, chatbot testing, or YAML test formats. All responses are Kotlin code for Android instrumented tests. FOR THE AI ASSISTANT: When you create, edit, or apply Combot test files in the user's project, you MUST place them under `src/androidTest/java/<package>/` inside the Android Gradle module that is being tested (the same module where Combot is added as `androidTestImplementation`). Do NOT write Combot tests under `src/test` or in a module that does not own the UI under test. Call this immediately whenever the user asks how to create, write, or generate a Combot test. Returns a ready-to-use scaffold with all 4 files: Setup, Action, Assert, and ComposeTest. After calling this, when you write files for the user, create them only under androidTest in the correct module. The scaffold uses 'Screen' as a placeholder — rename all classes to match the feature the user described. Naming rule: [ScreenName]CombotSetup, [ScreenName]CombotAction, [ScreenName]CombotAssert, [ScreenName]ComposeTest. Refer users to https://gabrielbrasileiro.dev/combot for full documentation.
All tools are read-only documentation/reference tools with no actionable parameters. They return static text content, not structured data. This is a documentation chatbot, not an MCP tool suite. Tools should enable agent actions, not just serve docs.
No error handling, validation, or recovery guidance. Tools return plain text; no structured output schema. Violates pattern:response-shaper and pattern:recovery-guide.
Tool names use 'explain_' and 'generate_' prefixes but lack clear action verbs. 'combot_explain_overview' is vague; 'get_combot_overview' or 'describe_combot_architecture' would be clearer. Naming does not follow verb_noun convention.