Skip to main content
Glama
alfred-voc-analysis-mcp

alfred-voc-analysis-mcp

Alfred VoC Analysis MCP v0.1

An MCP server that transforms Heum Alfred/DESK VoC facts into CX intelligence. The structure is explicitly separated into Fact → Analysis → Synthesis.

Architecture

  • fact.py: FactRepository to be implemented by DB/API adapters; Facts do not store AI interpretation.

  • analysis.py: computes overview, issue intelligence, CX concern, emerging signal, trend driver, and resolution effect in deterministic Python.

  • synthesis.py: assembles the detailed Report, Executive Brief, and improvement Planning Signal DTO.

  • server.py: FastMCP tool adapter. The analysis core does not depend on MCP or an external LLM.

The input schema preserves source extension fields with FactRecord(extra="allow"). It does not change the actual DB schema; production DB/API connections are added via the FactRepository adapter.

Related MCP server: NPS Chatbot MCP Server

MCP tools

  • get_voc_overview

  • analyze_issue_frequency, analyze_issue_severity, analyze_issue_persistence

  • analyze_unresolved_issues, rerank_issue_priorities, compare_issue_portfolio

  • analyze_customer_experience

  • detect_emerging_signals

  • analyze_voc_trends

  • analyze_resolution_effect

  • build_report_dataset, build_executive_brief, build_improvement_signals

Issue tools intentionally share one portfolio assessment so Frequency alone cannot contradict Priority Movement. Each issue result returns evidence, reason and confidence.

Run

python -m venv .venv
pip install -e ".[dev]"
pytest
alfred-voc-analysis-mcp

v0.1 ships an in-memory reference adapter. Embed the service and call configure_records, or implement FactRepository for voc-management DB/API.

Calibration

AnalysisConfig contains data-sufficiency and observation-window settings. Defaults are conservative technical defaults, not Heum policy. No opaque weighted score or fixed “N건=High” business rule is used.

Available Tools

14 tools
analyze_customer_experienceD

Inputs: end_date (required), start_date (required). Returns: result

analyze_issue_frequencyD

Inputs: end_date (required), start_date (required). Returns: result

analyze_issue_persistenceD

Inputs: end_date (required), start_date (required). Returns: result

analyze_issue_severityD

Inputs: end_date (required), start_date (required). Returns: result

analyze_resolution_effectD

Inputs: end_date (required), start_date (required). Returns: result

analyze_unresolved_issuesD

Inputs: end_date (required), start_date (required). Returns: result

build_executive_briefD

Inputs: end_date (required), start_date (required). Returns: object

build_improvement_signalsD

Inputs: end_date (required), start_date (required). Returns: object

build_report_datasetD

Inputs: end_date (required), start_date (required). Returns: object

compare_issue_portfolioD

Inputs: end_date (required), start_date (required). Returns: result

detect_emerging_signalsD

Inputs: end_date (required), start_date (required). Returns: result

get_voc_overviewD

Inputs: end_date (required), start_date (required), domain, channel, +3 more. Returns: object

rerank_issue_prioritiesD

Inputs: end_date (required), start_date (required). Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.1/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools are clearly separated by specific modifiers (frequency, severity, persistence, resolution effect), but a few pairs could be confused, such as analyze_unresolved_issues vs analyze_issue_persistence and detect_emerging_signals vs analyze_voc_trends.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern using predictable verbs like get, analyze, rerank, compare, detect, and build. The repeated analyze_ prefix is systematic and applied to distinct analytical dimensions.

    Tool Count5/5

    14 tools is well within the ideal 3-15 range for a specialized VOC analysis server. The set balances analytical tools, prioritization, comparison, and reporting outputs without unnecessary fragmentation.

    Completeness5/5

    The tool surface covers the full analytical workflow: overview, issue metrics, priorities, portfolio comparison, trends, emerging signals, resolution effectiveness, and report generation. There are no obvious gaps that would leave an agent unable to complete a VOC analysis task.

    Related MCP Connectors

    Related MCP Servers