Skip to main content
Glama

dhis2_android_configure_notifications

Configure push and local notifications for DHIS2 Android apps to alert users about sync status, data deadlines, and system messages using customizable triggers and settings.

Instructions

Set up push notifications and local notifications for DHIS2 Android app

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notificationTypesYesTypes of notifications to implement
pushProviderNoPush notification provider
triggersNoNotification triggers
schedulingNo
customizationNo

Implementation Reference

  • The MCP server request handler for the tool. It invokes generateNotificationsConfiguration from android-generators.ts with the tool arguments and returns the generated Android notifications configuration as text content.
    case 'dhis2_android_configure_notifications':
      const notificationsArgs = args as any;
      const notificationsConfig = generateNotificationsConfiguration(notificationsArgs);
      return {
        content: [
          {
            type: 'text',
            text: notificationsConfig,
          },
        ],
      };
  • The core generator function that creates a template for DHIS2 Android notifications configuration code, using the provided arguments (notably notificationTypes). Currently a stub implementation.
    export function generateNotificationsConfiguration(args: any): string {
      return `# DHIS2 Android Notifications Configuration
    
    Notification types: ${args.notificationTypes.join(', ')}
    
    ## Implementation details for notifications...
    `;
  • Permission registration mapping the tool to the 'canUseMobileFeatures' permission in PermissionSystem.TOOL_PERMISSIONS.
    ['dhis2_android_configure_notifications', 'canUseMobileFeatures'],
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'Set up,' implying a configuration or write operation, but fails to detail critical aspects like whether this is idempotent, requires specific permissions, impacts app behavior, or has side effects. This leaves significant gaps for a tool with multiple parameters and nested objects.

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 wasted words. It front-loads the core purpose ('Set up push notifications and local notifications') and specifies the context ('for DHIS2 Android app'), making it easy to parse quickly.

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?

Given the complexity (5 parameters with nested objects, no output schema, and no annotations), the description is insufficient. It doesn't address behavioral traits, output expectations, or error handling, leaving the agent with incomplete guidance for a configuration tool that likely involves app changes.

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 60%, and the description adds no parameter-specific information beyond what the schema provides. It doesn't explain relationships between parameters (e.g., how 'pushProvider' relates to 'notificationTypes') or provide usage examples. The baseline is 3 since the schema covers most parameters adequately, but the description doesn't compensate for the 40% coverage gap.

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 ('Set up') and target resources ('push notifications and local notifications for DHIS2 Android app'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'dhis2_android_configure_camera' or 'dhis2_android_configure_storage' beyond the notification focus, preventing a perfect score.

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 explicit guidance is provided on when to use this tool versus alternatives. The description lacks context about prerequisites, dependencies, or scenarios where this configuration is needed, leaving the agent to infer usage from the tool name alone.

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