Skip to main content
Glama
gcorroto

Asterisk S2S MCP Server

by gcorroto

phone_health_check

Assess and monitor the health status of your telephone system with this diagnostic tool, ensuring reliable performance for automated conversational phone calls using Asterisk and Speech-to-Speech capabilities.

Instructions

Verificar el estado de salud del sistema telefónico

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • index.ts:172-188 (registration)
    Registration of the MCP tool 'phone_health_check' with empty input schema and inline handler function that invokes phoneTools.healthCheck() and formats a status response with icons and details.
      "phone_health_check",
      "Verificar el estado de salud del sistema telefónico",
      {},
      async () => {
        const result = await phoneTools.healthCheck();
    
        const statusIcon = result.status === 'healthy' ? '✅' : '❌';
        const phoneIcon = result.phoneAssistant ? '📞' : '📵';
    
        return {
          content: [{ 
            type: "text", 
            text: `${statusIcon} **Estado del Sistema: ${result.status.toUpperCase()}**\n\n${phoneIcon} **Asistente telefónico:** ${result.phoneAssistant ? 'Conectado' : 'Desconectado'}\n📊 **Llamadas activas:** ${result.activeCalls}\n🕐 **Verificado:** ${result.timestamp}${result.lastError ? `\n❌ **Último error:** ${result.lastError}` : ''}`
          }],
        };
      }
    );
  • Supporting healthCheck helper function in phoneTools that delegates to phoneOps.healthCheck() and adds a timestamp to the result.
    export async function healthCheck(): Promise<{
      status: 'healthy' | 'unhealthy';
      phoneAssistant: boolean;
      activeCalls: number;
      lastError?: string;
      timestamp: string;
    }> {
      const health = await phoneOps.healthCheck();
      
      return {
        ...health,
        timestamp: new Date().toISOString()
      };
    }
  • Core healthCheck implementation that uses the PhoneClient to check the phone assistant health, counts active calls, and handles errors.
    export async function healthCheck(): Promise<{
      status: 'healthy' | 'unhealthy';
      phoneAssistant: boolean;
      activeCalls: number;
      lastError?: string;
    }> {
      try {
        const client = getPhoneClient();
        const isHealthy = await client.healthCheck();
        
        return {
          status: isHealthy ? 'healthy' : 'unhealthy',
          phoneAssistant: isHealthy,
          activeCalls: activeCalls.size
        };
      } catch (error) {
        return {
          status: 'unhealthy',
          phoneAssistant: false,
          activeCalls: activeCalls.size,
          lastError: error instanceof Error ? error.message : 'Unknown error'
        };
      }
    }
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 'verificar' implies a read-only operation, the description doesn't specify whether this tool requires authentication, has rate limits, returns specific health metrics versus general status, or what format the output takes. For a tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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, clear Spanish sentence that directly states the tool's purpose without any unnecessary words. It's perfectly front-loaded with the essential information and wastes no space on redundant or irrelevant details.

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 that this is a health-check tool with no annotations, no output schema, and multiple sibling tools that might overlap in functionality, the description is insufficiently complete. It doesn't explain what constitutes 'health' versus general status, what metrics or checks are performed, or how the results differ from other status-related tools. For a tool in this context, more specificity is needed.

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 zero parameters, and schema description coverage is 100% (since there are no parameters to describe). The description appropriately doesn't discuss parameters since none exist. The baseline for zero parameters with full schema coverage is 4, as there's no need for parameter explanation in the description.

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 'Verificar el estado de salud del sistema telefónico' clearly states the tool's purpose: to verify/check the health status of the telephone system. It uses a specific verb ('verificar') and resource ('sistema telefónico'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'phone_get_status' or 'phone_get_metrics', which might provide related status information.

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 that might provide overlapping or related information (phone_get_status, phone_get_metrics, phone_get_active_calls), there's no indication of what makes this health check distinct or when it should be preferred over other status-checking tools.

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

Related 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/gcorroto/mcp-s2s-asterisk'

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