Skip to main content
Glama

dhis2_android_setup_offline_analytics

Configure offline analytics and reporting for DHIS2 Android app by selecting features, chart types, aggregation levels, and export options to enable data analysis without internet connectivity.

Instructions

Configure offline analytics and reporting capabilities for DHIS2 Android app

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
analyticsFeaturesYesAnalytics features to include
chartTypesNoChart types to support
dataAggregationNo
cachingNo
exportNo

Implementation Reference

  • Handler function that receives tool arguments, calls the generator helper, and returns markdown configuration as tool response content.
    case 'dhis2_android_setup_offline_analytics':
      const analyticsArgs = args as any;
      const analyticsConfig = generateOfflineAnalyticsConfiguration(analyticsArgs);
      return {
        content: [
          {
            type: 'text',
            text: analyticsConfig,
          },
        ],
      };
  • Helper function that generates a markdown template for DHIS2 Android offline analytics setup based on input arguments (currently placeholder implementation).
    export function generateOfflineAnalyticsConfiguration(args: any): string {
      return `# DHIS2 Android Offline Analytics Configuration
    
    Analytics features: ${args.analyticsFeatures.join(', ')}
    
    ## Implementation details for offline analytics...
    `;
    }
  • Tool permission registration mapping the tool name to required 'canUseMobileFeatures' permission for access filtering.
    ['dhis2_android_setup_offline_analytics', '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 states 'configure' but doesn't clarify if this is a one-time setup, requires specific permissions, modifies app files, has side effects, or what happens on success/failure. For a configuration tool with complex parameters, this lack of behavioral context is a significant gap.

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 purpose without unnecessary words. It's front-loaded with the core action and target, 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 tool's complexity (5 parameters with nested objects, no output schema, and no annotations), the description is inadequate. It doesn't explain the scope of configuration, expected outcomes, or how it integrates with other DHIS2 Android setup tools. For a tool with rich input schema but poor documentation, more context is needed to guide effective use.

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 schema descriptions. The tool description doesn't add any parameter-specific information beyond the generic 'offline analytics and reporting capabilities', failing to explain what each parameter controls or how they interact. This leaves key parameters like 'dataAggregation' and 'caching' without semantic context.

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 ('configure') and target ('offline analytics and reporting capabilities for DHIS2 Android app'), making the purpose understandable. However, it doesn't explicitly differentiate this from sibling tools like 'dhis2_android_setup_sync' or 'dhis2_android_configure_notifications', which might also involve configuration aspects.

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. It doesn't mention prerequisites, timing (e.g., during app setup vs. post-deployment), or how it relates to sibling tools like 'dhis2_android_setup_sync' for data synchronization, leaving the agent to infer usage context.

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