Skip to main content
Glama

dhis2_configure_app_manifest

Generate or update the manifest.webapp configuration file for DHIS2 applications, specifying app metadata, entry points, permissions, and developer details.

Instructions

Generate or update manifest.webapp file for DHIS2 app

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesApp name
versionYesApp version (e.g., "1.0.0")
descriptionYesApp description
developerYes
iconsNo
activitiesYes
authoritiesNoRequired DHIS2 authorities/permissions
appTypeNoType of DHIS2 application
launch_pathNoLaunch path for the app

Implementation Reference

  • Core handler function that generates DHIS2 app manifest content from input parameters, formats it as markdown with installation instructions and examples.
    export function generateManifestContent(args: any): string {
      const { name, version, description, developer, icons, activities, authorities, appType, launch_path } = args;
    
      const manifest = {
        version: version || '1.0.0',
        name: name,
        description: description,
        developer: {
          name: developer.name,
          ...(developer.email && { email: developer.email })
        },
        icons: icons || {
          "48": "./icon-48.png",
          "128": "./icon-128.png"
        },
        activities: activities,
        ...(authorities && { authorities }),
        ...(appType && { appType }),
        ...(launch_path && { launch_path })
      };
    
      return `# DHIS2 App Manifest Configuration
    
    ## Generated manifest.webapp
    \`\`\`json
    ${JSON.stringify(manifest, null, 2)}
    \`\`\`
    
    ## Installation Instructions
    1. Save the above content as \`public/manifest.webapp\` in your app directory
    2. Ensure icon files exist at the specified paths
    3. Update authorities array with required permissions
    4. Customize the launch_path if needed
    
    ## Authority Examples
    \`\`\`json
    "authorities": [
      "F_METADATA_IMPORT",
      "F_METADATA_EXPORT", 
      "F_DATA_VALUE_ADD",
      "F_DATAVALUE_ADD_WITHIN_ASSIGNED_ORGUNIT",
      "F_TRACKED_ENTITY_INSTANCE_ADD",
      "F_PROGRAM_ENROLLMENT"
    ]
    \`\`\`
    
    ## App Type Options
    - **APP**: Standard DHIS2 application
    - **DASHBOARD_WIDGET**: Dashboard plugin/widget
    - **TRACKER_DASHBOARD_WIDGET**: Tracker-specific dashboard widget
    `;
    }
  • MCP server request handler that receives tool call parameters and invokes the generateManifestContent function, returning the result as text content.
    case 'dhis2_configure_app_manifest':
      const manifestArgs = args as any;
      const manifestContent = generateManifestContent(manifestArgs);
      return {
        content: [
          {
            type: 'text',
            text: manifestContent,
          },
        ],
      };
  • Tool permission registration mapping the tool to 'canConfigureApps' permission requirement.
    ['dhis2_configure_app_manifest', 'canConfigureApps'],
  • src/index.ts:19-35 (registration)
    Import of the generateManifestContent handler function into the main MCP server index.
      generateWebAppInitInstructions,
      generateManifestContent,
      generateBuildSystemConfig,
      generateDevEnvironmentConfig,
      generateAppRuntimeConfig,
      generateAuthenticationPatterns,
      generateUIComponents,
      generateUIFormPatterns,
      generateUIDataDisplayPatterns,
      generateUINavigationLayout,
      generateDesignSystemConfig,
      generateAndroidMaterialForm,
      generateAndroidListAdapter,
      generateAndroidNavigationDrawer,
      generateAndroidBottomSheet,
      generateTestSetup
    } from './webapp-generators.js';
Behavior2/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 mentions 'Generate or update' but does not specify if this is a read-only or destructive operation, what permissions are needed, or how errors are handled. For a tool that likely modifies files, this lack of detail is a significant gap in transparency.

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 directly states the tool's function without unnecessary words. It is appropriately sized and front-loaded, making it easy to understand at a glance.

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 (9 parameters, nested objects) and lack of annotations or output schema, the description is insufficient. It does not explain what the tool returns, how it handles missing parameters, or the implications of generating vs. updating a manifest file, leaving critical gaps for an agent to use it effectively.

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?

The description does not add any parameter-specific information beyond what the input schema provides. With a schema description coverage of 67%, the baseline is 3, as the schema handles most documentation, but the description fails to compensate for the 33% gap or clarify the purpose of parameters like 'authorities' or 'appType'.

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 or update') and the target resource ('manifest.webapp file for DHIS2 app'), making the purpose specific and understandable. However, it does not differentiate from sibling tools like 'dhis2_init_webapp' or 'dhis2_generate_app_runtime_config', which might have overlapping or related functions, so it lacks explicit sibling distinction.

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, such as whether it's for initial setup, updates, or specific app types. With many sibling tools in the DHIS2 context, this omission leaves the agent without clear usage context or exclusions.

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