Skip to main content
Glama

dhis2_android_configure_ui_patterns

Generate Android UI patterns and components for DHIS2 apps using Jetpack Compose, XML layouts, or hybrid frameworks with accessibility and localization support.

Instructions

Generate Android UI patterns and components for DHIS2 apps

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uiFrameworkYesUI framework to use
componentsYesUI components to generate
designSystemNo
accessibilityNo
localizationNo

Implementation Reference

  • Main handler for the tool call: extracts arguments and invokes the UI configuration generator function.
    const androidUIArgs = args as any;
    const uiConfig = generateAndroidUIConfiguration(androidUIArgs);
    return {
      content: [
        {
          type: 'text',
          text: uiConfig,
        },
      ],
    };
  • Core generator function that produces the tool's output: a markdown template for Android UI configuration based on input args.
    export function generateAndroidUIConfiguration(args: any): string {
      return `# DHIS2 Android UI Configuration
    
    UI Framework: ${args.uiFramework}
    Components: ${args.components.join(', ')}
    
    ## Implementation details for UI patterns...
    `;
  • Tool permission registration: requires 'canUseMobileFeatures' permission to access.
    ['dhis2_android_configure_ui_patterns', 'canUseMobileFeatures'],
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Generate' implies a creation/write operation, but the description doesn't specify what exactly gets generated (code files? configuration? documentation?), whether this requires specific permissions, what the output format is, or any side effects. For a tool with 5 parameters and complex nested objects, this is inadequate behavioral context.

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 that gets straight to the point with zero wasted words. It's appropriately sized for a tool name that already conveys the domain (DHIS2 Android) and action (configure).

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

Completeness2/5

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

For a complex tool with 5 parameters (including nested objects), no annotations, no output schema, and only 40% schema description coverage, the description is insufficient. It doesn't explain what 'generate' means in practical terms, what the output looks like, how the various configuration options interact, or provide any context about the DHIS2 Android ecosystem that would help an agent use this tool effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 40%, meaning most parameters lack documentation in the schema. The description doesn't compensate by explaining any parameters or their relationships. It mentions 'UI patterns and components' which vaguely relates to the 'components' parameter, but provides no additional context about the other 4 parameters (uiFramework, designSystem, accessibility, localization) or how they interact.

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 clearly states the action ('Generate') and target ('Android UI patterns and components for DHIS2 apps'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'dhis2_generate_ui_form_patterns' or 'dhis2_generate_ui_navigation_layout', which appear to be more specialized versions of similar functionality.

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?

The description provides no guidance on when to use this tool versus alternatives. With multiple sibling tools that appear to generate specific UI components (e.g., 'android_generate_bottom_sheet', 'android_generate_list_adapter'), there's no indication whether this is a comprehensive tool versus those specialized ones, or what context would warrant choosing this broader configuration tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Dradebo/dhis2-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server