alfred-voc-analysis-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
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.
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.
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.
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.