Skip to main content
Glama

dhis2_register_compatible_server

Register compatible MCP servers for composition workflows by providing name, version, capabilities, and description to enable integration with DHIS2 health information systems.

Instructions

Register information about a compatible MCP server for composition workflows

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the MCP server
versionYesVersion of the MCP server
capabilitiesYesServer capabilities
descriptionYesDescription of the server

Implementation Reference

  • Main handler implementation for the 'dhis2_register_compatible_server' tool. Registers a compatible MCP server by calling multiServerComposition.registerCompatibleServer and returns success message with next steps.
          case 'dhis2_register_compatible_server':
            const serverRegistrationArgs = args as {
              name: string;
              version: string;
              capabilities: Array<{ domain: string; operations: string[]; version: string }>;
              description: string;
            };
            
            multiServerComposition.registerCompatibleServer({
              name: serverRegistrationArgs.name,
              version: serverRegistrationArgs.version,
              capabilities: serverRegistrationArgs.capabilities,
              description: serverRegistrationArgs.description,
              compatibleWith: ['dhis2-mcp'],
              compositionMode: true
            });
            
            auditLogger.log({
              toolName: name,
              parameters: serverRegistrationArgs,
              outcome: 'success',
              dhis2Instance: dhis2Client?.baseURL,
              userId: currentUser?.username,
              executionTime: Date.now() - startTime
            });
            
            return {
              content: [{
                type: 'text',
                text: `āœ… Successfully registered MCP server: ${serverRegistrationArgs.name} v${serverRegistrationArgs.version}
    
    **Capabilities Added:**
    ${serverRegistrationArgs.capabilities.map(cap => 
      `  • ${cap.domain}: ${cap.operations.join(', ')}`
    ).join('\n')}
    
    šŸ”— **Multi-Server Workflows:** Now enabled with ${multiServerComposition.getCompatibleServers().length} registered server(s)
    
    šŸ’” **Next Steps:**
      • Use dhis2_get_composition_recommendations to see integration suggestions
      • Use dhis2_export_for_composition to share data with other servers
      • Check dhis2_get_composition_examples for workflow ideas`
              }]
            };
  • Core helper method that stores the compatible server information in a Map for multi-server composition tracking.
    registerCompatibleServer(serverInfo: MCPServerInfo): void {
      this.compatibleServers.set(serverInfo.name, serverInfo);
      console.log(`[COMPOSITION] Registered compatible server: ${serverInfo.name}`);
    }
  • Type definition for the MCPServerInfo used in registration, defining the structure expected by the tool.
    export interface MCPServerInfo {
      name: string;
      version: string;
      capabilities: ServerCapability[];
      compatibleWith: string[];
      compositionMode: boolean;
      description: string;
      authors?: string[];
      documentation?: string;
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states this is a registration tool, implying a write/mutation operation, but doesn't address critical aspects like authentication requirements, whether this creates persistent records, potential side effects, error handling, or what happens if duplicate servers are registered. This leaves significant behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/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 appropriately sized for a registration tool, though it could potentially benefit from a brief second sentence about usage context given the many sibling tools.

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 mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what 'register' entails operationally, what format the registration takes, whether there are validation rules, or what the expected outcome is. The agent lacks crucial context about this write operation's behavior and results.

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?

With 100% schema description coverage, the schema already documents all 4 parameters thoroughly. The description doesn't add any meaningful parameter semantics beyond what's in the schema (e.g., it doesn't explain what 'compatible' means for capabilities or how this information is used in composition workflows). The baseline score of 3 reflects adequate but not enhanced parameter understanding.

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 ('Register information') and the resource ('compatible MCP server for composition workflows'), providing a specific purpose. However, it doesn't explicitly differentiate this registration tool from other DHIS2 tools like 'dhis2_export_for_composition' or 'dhis2_get_composition_examples', which prevents 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?

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or exclusions. With many sibling tools focused on composition workflows (e.g., 'dhis2_export_for_composition', 'dhis2_get_composition_recommendations'), the lack of contextual usage information leaves the agent guessing about appropriate scenarios.

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