Skip to main content
Glama

Related Servers

Alternatives to CustoVox MCP servers

No user-submitted related servers found.

    Related Servers

    TDQS

    A3.8/5.0

    Scored across 4 tools

    Disambiguation4/5

    Each tool has a distinct role: analyze_call writes/ingests, get_call_insights aggregates, search_feedback does sentence-level lookup, and suggest_actions derives recommendations for one call. The main soft spot is that suggest_actions implicitly requires a call already analyzed by analyze_call (and a call id), and get_call_insights vs search_feedback both report on past calls, though their granularity is clearly described.

    Naming Consistency5/5

    All four names follow a clean verb_noun snake_case pattern: analyze_call, get_call_insights, search_feedback, suggest_actions. The verb choice also signals intent well (analyze=write, get=read aggregate, search=lookup, suggest=derive), with no style mixing.

    Tool Count4/5

    Four tools is a tight, well-scoped surface for a local call-analytics server, and each tool earns its place. It sits at the low end of the ideal range, with no explicit list/get-calls tool to round it out.

    Completeness3/5

    Core flow (analyze → aggregate → search → suggest) is covered, but there is no way to fetch a single stored call's analysis by id, nor to delete/re-analyze a call, which matters for a local database-backed tool. Agents must rely on aggregate or search results to recover call ids.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues