Skip to main content
Glama
sloth-wq

Prompt Auto-Optimizer MCP

by sloth-wq

gepa_recovery_status

Check disaster recovery status and health information to monitor system resilience and operational continuity.

Instructions

Get comprehensive disaster recovery status and health information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
includeMetricsNoInclude detailed metrics in response

Implementation Reference

  • Tool registration in the TOOLS array, including name, description, and input schema.
    {
      name: 'gepa_recovery_status',
      description: 'Get comprehensive disaster recovery status and health information',
      inputSchema: {
        type: 'object',
        properties: {
          includeMetrics: {
            type: 'boolean',
            default: true,
            description: 'Include detailed metrics in response'
          }
        }
      }
    },
  • Handler registration in the switch statement for tool calls.
    case 'gepa_recovery_status':
      return await this.getRecoveryStatus(args as {
        includeMetrics?: boolean;
      });
  • Main handler function that executes the tool logic by calling disaster recovery system's health check and dashboard methods, then formats and returns the status information.
      private async getRecoveryStatus(params: {
        includeMetrics?: boolean;
      }): Promise<{ content: { type: string; text: string; }[] }> {
        const { includeMetrics = true } = params;
    
        try {
          await this.disasterRecovery.initialize();
          
          const health = await this.disasterRecovery.performHealthCheck();
          const dashboard = await this.disasterRecovery.getRecoveryDashboard();
    
          return {
            content: [
              {
                type: 'text',
                text: `# Disaster Recovery Status
    
    ## Overall System Health: ${health.overall.toUpperCase()}
    
    ### System Components
    ${Object.entries(health.systems).map(([system, systemHealth]) => 
      `- **${system}**: ${systemHealth.status.toUpperCase()} (Last check: ${systemHealth.lastCheck.toISOString()})`
    ).join('\n')}
    
    ### Recovery Dashboard
    - **System Status**: ${dashboard.systemStatus.overall.toUpperCase()}
    - **Active Recoveries**: ${dashboard.systemStatus.activeRecoveries}
    - **Recent Failures**: ${dashboard.systemStatus.recentFailures}
    - **Total Executions**: ${dashboard.recoveryHistory.totalExecutions}
    - **Success Rate**: ${(dashboard.recoveryHistory.successRate * 100).toFixed(1)}%
    
    ### Metrics
    - **Backups Available**: ${dashboard.metrics.backupsAvailable}
    - **Quarantined Items**: ${dashboard.metrics.quarantinedItems}
    - **Critical Components**: ${dashboard.metrics.criticalComponents}
    - **Last Backup Age**: ${dashboard.metrics.lastBackupAge} minutes
    
    ${dashboard.recommendations.length > 0 ? `### Recommendations
    ${dashboard.recommendations.map(rec => `- ${rec}`).join('\n')}` : ''}
    
    ${dashboard.alerts.length > 0 ? `### Active Alerts
    ${dashboard.alerts.map(alert => `🚨 **${alert.title}** (${alert.severity}): ${alert.description}`).join('\n')}` : ''}
    
    ${includeMetrics ? `### Detailed Metrics
    ${Object.entries(health.systems).map(([system, systemHealth]) => 
      `#### ${system.charAt(0).toUpperCase() + system.slice(1)}
    ${Object.entries(systemHealth.metrics || {}).map(([key, value]) => `  - ${key}: ${value}`).join('\n')}`
    ).join('\n\n')}` : ''}`,
              },
            ],
          };
        } catch (error) {
          throw new Error(`Failed to get recovery status: ${error instanceof Error ? error.message : 'Unknown error'}`);
        }
      }
  • Input schema definition for the tool, specifying optional includeMetrics boolean parameter.
    inputSchema: {
      type: 'object',
      properties: {
        includeMetrics: {
          type: 'boolean',
          default: true,
          description: 'Include detailed metrics in response'
        }
      }
    }
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. While it implies a read-only operation ('Get'), it lacks details on permissions, rate limits, response format, or whether it's safe to invoke frequently. For a tool that likely interacts with critical disaster recovery systems, this 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 front-loads the core purpose without unnecessary words. Every part of the sentence ('Get comprehensive disaster recovery status and health information') contributes directly to understanding the tool's function, making it highly concise and well-structured.

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 lack of annotations and output schema, the description is incomplete for a tool that likely returns complex disaster recovery data. It doesn't explain what 'comprehensive' entails, what health information is included, or how the response is structured. For a tool in a critical domain with no structured output guidance, this leaves too many unknowns for effective use.

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 input schema has 100% description coverage, with the single parameter 'includeMetrics' clearly documented in the schema. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline score of 3 without compensating or detracting.

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 ('disaster recovery status and health information'), making it immediately understandable. However, it doesn't explicitly distinguish this tool from potential sibling tools like 'gepa_list_backups' or 'gepa_integrity_check' that might also provide status-related information, 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?

The description provides no guidance on when to use this tool versus alternatives. With multiple sibling tools related to backups, recovery, and status checks (e.g., 'gepa_list_backups', 'gepa_integrity_check'), there is no indication of when this comprehensive status check is preferred over more specific tools, leaving the agent without 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/sloth-wq/prompt-auto-optimizer-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server