Skip to main content
Glama

dhis2_get_server_info

Retrieve server details and available capabilities for the DHIS2 health information system to understand available functionality.

Instructions

Get information about this MCP server and its composition capabilities

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the 'dhis2_get_server_info' tool. Calls MultiServerComposition.getServerInfo() and formats a comprehensive text response detailing the MCP server's name, version, capabilities, compatible servers, and multi-server composition status.
          case 'dhis2_get_server_info':
            const serverInfo = multiServerComposition.getServerInfo();
            
            auditLogger.log({
              toolName: name,
              parameters: {},
              outcome: 'success',
              dhis2Instance: dhis2Client?.baseURL,
              userId: currentUser?.username,
              executionTime: Date.now() - startTime
            });
            
            return {
              content: [{
                type: 'text',
                text: `šŸ–„ļø DHIS2 MCP Server Information
    
    **Server Details:**
      • Name: ${serverInfo.name}
      • Version: ${serverInfo.version}
      • Composition Mode: ${serverInfo.compositionMode ? 'Enabled' : 'Disabled'}
      
    **Description:** ${serverInfo.description}
    
    **Capabilities:**
    ${serverInfo.capabilities.map(cap => 
      `  • **${cap.domain}** (v${cap.version}): ${cap.operations.join(', ')}`
    ).join('\n')}
    
    **Compatible MCP Servers:**
    ${serverInfo.compatibleWith.map(server => `  • ${server}`).join('\n')}
    
    **Currently Registered Servers:** ${multiServerComposition.getCompatibleServers().length}
    ${multiServerComposition.getCompatibleServers().map(server => 
      `  • ${server.name} v${server.version}: ${server.description}`
    ).join('\n') || '  • No servers registered yet'}
    
    šŸ”— **Integration Status:** 
    ${multiServerComposition.getCompatibleServers().length > 0 ? 
      `āœ… Ready for multi-server workflows with ${multiServerComposition.getCompatibleServers().length} registered server(s)` : 
      'āš ļø  No compatible servers registered. Use dhis2_register_compatible_server to enable workflows.'
    }`
              }]
            };
  • Core helper method invoked by the tool handler. Returns a deep copy of the static server information object containing capabilities, compatible servers, and composition metadata.
    getServerInfo(): MCPServerInfo {
      return { ...this.serverInfo };
    }
  • Static server information object initialized in the MultiServerComposition constructor, providing the core data returned by getServerInfo() including capabilities across health-data, DHIS2 API, mobile/web development domains.
    this.serverInfo = {
      name: 'dhis2-mcp',
      version: '1.0.0',
      capabilities: [
        {
          domain: 'health-data',
          operations: ['data-collection', 'analytics', 'reporting', 'validation'],
          version: '2.40+'
        },
        {
          domain: 'dhis2-api',
          operations: ['metadata-management', 'data-import-export', 'user-management'],
          version: '1.0.0'
        },
        {
          domain: 'mobile-development',
          operations: ['android-sdk', 'offline-sync', 'location-services'],
          version: '1.0.0'
        },
        {
          domain: 'web-development',
          operations: ['app-platform', 'ui-components', 'debugging'],
          version: '1.0.0'
        }
      ],
      compatibleWith: [
        'github-mcp',
        'slack-mcp',
        'database-mcp',
        'git-mcp',
        'filesystem-mcp',
        'email-mcp'
      ],
      compositionMode: true,
      description: 'Comprehensive DHIS2 development and management MCP server',
      authors: ['DHIS2 Community'],
      documentation: 'https://github.com/dhis2/mcp-server'
    };
  • Instantiation of the MultiServerComposition class used by the tool handler.
    let multiServerComposition: MultiServerComposition = new MultiServerComposition();
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 the tool retrieves server and composition capability information but doesn't describe what specific information is returned (e.g., server version, supported features, composition limits), whether it requires authentication, or any rate limits. This leaves significant gaps for an agent to understand the tool's behavior.

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 is front-loaded with the core action ('Get information'), making it easy for an agent to parse quickly. Every part of the sentence earns its place by specifying the target ('this MCP server') and scope ('composition capabilities').

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 (likely low, as it retrieves server info) but with no annotations and no output schema, the description is incomplete. It doesn't explain what 'composition capabilities' entail or what format the information is returned in, leaving the agent uncertain about the tool's output and usage context. More detail would help compensate for the lack of structured data.

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 tool has 0 parameters, and the input schema has 100% description coverage (though empty). The description doesn't need to explain parameters, so it appropriately avoids mentioning any. A baseline of 4 is applied since no parameters exist, and the description doesn't introduce confusion about inputs.

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 tool's purpose with a specific verb ('Get') and resource ('information about this MCP server and its composition capabilities'). It distinguishes itself from most sibling tools which focus on Android configuration, DHIS2 operations, or UI generation, though it doesn't explicitly differentiate from other 'get' tools like dhis2_get_audit_log or dhis2_get_composition_examples.

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., at server startup or for diagnostics), or how it differs from other information-retrieval tools in the sibling list, such as dhis2_get_permission_info or dhis2_get_composition_recommendations.

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