android-dev-mcp

get_architecture_patterns

Retrieve MVVM, Hilt DI, ViewModel, StateFlow, and Coroutine patterns to implement standard Android architecture in your project.

Instructions

Returns MVVM, Hilt DI, ViewModel, StateFlow, and Coroutine patterns.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_architecture_patterns"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.1Aug 2, 2026

TDQS

B3.3/5.0

Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only lists the patterns returned and does not mention whether the tool is read-only, static, or has any side effects or rate limits. This is a significant transparency gap for a get-type tool.

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?

The description is a single, efficient sentence with no unnecessary words. It directly states the tool's function and the list of patterns, earning full marks for conciseness.

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?

The tool is simple (0 params, no output schema), but the description lacks clarity on what 'patterns' means—whether it returns code snippets, textual explanations, or links. It is minimally adequate but could be more complete by specifying the return format or content type.

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?

The input schema is empty with no parameters, so schema description coverage is effectively 100%. Per guidelines, a baseline of 4 is appropriate for zero-parameter tools; the description adds no parameter information because none exist.

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 the tool 'Returns MVVM, Hilt DI, ViewModel, StateFlow, and Coroutine patterns.' This specifies both the action (returns) and the resource (specific architecture patterns), distinguishing it from sibling tools like get_api_backend_patterns and get_player_patterns.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternatives. The description simply states what it returns, with no mention of appropriate contexts, exclusions, or relationships to sibling tools like get_full_context or get_project_structure.

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