Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CUSTOVOX_CALLS_DEMONoSet to 1 to run the custovox-calls server in demo mode, e.g. `claude mcp add custovox-calls-demo --env CUSTOVOX_CALLS_DEMO=1 -- uvx custovox-calls`.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
analyze_callA

Analyze one customer-service call and save the result in the local database.

    source: a local audio file, an http(s) URL to an audio file, a local JSON file of transcript
    segments [{start, end, text}], or a demo call id (demo-1 ... demo-6).
    started_at: ISO date-time of the call (default: now). language: e.g. "fr" or "en" (audio only).
    Returns sentiment, contact reasons, key moments (complaint, churn threat, agent promise) and a
    transcript excerpt. Runs locally: audio is transcribed on this machine.
get_call_insightsA

Summary of the analyzed calls over a period: number of calls, minutes, mean customer sentiment, contact reasons, key moments, churn threats and the most negative calls. since / until: ISO dates, e.g. "2026-11-01" (until is exclusive). Read-only.

search_feedbackA

Search what was said in the analyzed calls. All words must appear in the same sentence; case and accents are ignored. speaker: "customer" (default), "agent", or null for both. Returns the matching sentences with their call id and time. Read-only.

suggest_actionsA

Suggest follow-up actions for an analyzed call: manager alert (churn threat or complaint), customer callback (to check an agent promise is kept), CRM ticket (negative sentiment). Each action has a priority, a reason and the sentence that triggered it. Sends nothing.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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