android-dev-mcp

verify_ui

Renders a @Preview composable via Android CLI and cross-checks its semantics tree against Compose standards to validate UI compliance. Returns the render command and standards to validate against.

Instructions

Agentic workflow: renders a @Preview composable via Android CLI and cross-checks its semantics tree against ITGD Compose standards. Returns render command + standards to validate against.

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": {
      "file_path": "<file_path>",
      "composable_name": "<composable_name>"
    },
    "name": "verify_ui"
  }
}

Input Schema

Name	Required	Description	Default
`file_path`	Yes	Path to the Kotlin file containing the @Preview composable.
`composable_name`	Yes	Name of the composable @Preview function to render.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.1Aug 2, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the rendering and checking process and the return value, but does not mention side effects, prerequisites, or failure modes. The workflow nature is mentioned but not detailed.

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?

The description is a single sentence that packs a lot of relevant information: the rendering, the cross-check, and the return value. It is concise, though somewhat dense and could be slightly clearer with structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex workflow tool, the description provides a high-level overview but lacks details on prerequisites, interpretation of results, and integration with sibling tools. Since there is no output schema, the return value is mentioned but not elaborated. The complexity is moderate, and the description is adequate but not complete.

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% for both parameters (file_path and composable_name), each with clear descriptions. The tool description does not add additional meaning beyond the schema, 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 clearly states a specific verb + resource: renders a @Preview composable via Android CLI and cross-checks its semantics tree against ITGD Compose standards. It also mentions the return value, distinguishing it from siblings like run_android_cli and get_ui_compose_standards.

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 implied as part of an agentic workflow for UI verification, but there is no explicit when-to-use or when-not-to-use guidance, nor alternatives named. It could be clearer about when to choose this over simply getting standards or running CLI commands.

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