wealify-kpi-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KPI_BASE_URL | No | Base URL for the KPI API. Default is https://kpi.wealify.com/api/v1. | https://kpi.wealify.com/api/v1 |
| PAPERCLIP_READ_TOKEN | Yes | Read-only token for authentication. Must match the token set in the backend. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| kpi_healthA | Health/identity probe — confirms the read token works and the dashboard is reachable. |
| kpi_scoring_periodA | Scoring-period state (OPEN | LOCKED) for a month. Use before nudging Leads or reading 'final' numbers. |
| kpi_scoring_coverageC | Active members who still lack data to be scored this month (so a Lead can be reminded before lock). |
| kpi_member_kpiA | Full KPI breakdown for a member (engine1 commission, engine2 squad-bonus, clawback, total payout) for a quarter. |
| kpi_alertsC | Derived alert signals for a quarter: squad below revenue floor, bonus pool hitting the 15% GP cap, sync staleness. |
| kpi_overviewA | Company-wide overview for a quarter: per-squad performance, sales leaderboard, chapter averages, engine-3 status. Use for CEO/Finance digests. |
| kpi_chapterC | Chapter aggregate + per-member metric breakdown. chapter = SALES | PRODUCT | GROWTH | ENGINEER. |
| kpi_chapter_monthlyA | Số liệu chapter theo TỪNG THÁNG. Dùng khi cần xem "tháng 5 Sales đạt bao nhiêu?". Với SALES: trả về GTV, số deal, số KH từng người trong tháng. Với chapter khác: revenue squad tháng đó + metrics. |
| kpi_membersA | Active roster: members + Leads (id, name, email, role, chapter, squad) — so you know WHO to message and can iterate. Optional filters: chapter, squadId. |
| kpi_rubricsA | Rubric thresholds & criteria for a chapter in a quarter. Returns metric keys, fail/standard/excellent thresholds, multipliers, and data sources. Use to understand scoring rules before generating reports. |
| kpi_sla_statusA | Tiến độ chấm điểm của Lead theo tháng: Lead nào đã chấm xong cho team, ai đang quá hạn. Dùng để nhắc Lead trước hạn chót (ngày 4 hàng tháng, 17:00 ICT) hoặc đánh dấu vi phạm thời hạn. |
| kpi_rubric_docA | Full rubric document (markdown) for a chapter — contains scoring criteria, thresholds, behavioral descriptions, data sources. Use this when asked about "rubric chapter X" or when you need to understand how KPIs are scored. Available: SALES, PRODUCT, ENGINEER, GROWTH, MARKETING. |
| kpi_docs_listA | List all available document files in the mcp/docs/ directory. Returns filenames so agents know what reference documents are available. |
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 13 tools
Each tool has a distinct purpose: alerts, chapter aggregates, monthly breakdowns, member KPI, roster, overview, rubric document, rubric thresholds, scoring coverage, period state, and SLA status. No two tools overlap; even kpi_chapter and kpi_chapter_monthly are clearly differentiated by temporal aggregation.
All tools follow a consistent 'kpi_<noun>' or 'kpi_<noun>_<subnoun>' pattern (e.g., kpi_alerts, kpi_chapter_monthly, kpi_scoring_coverage). No mixing of conventions, camelCase, or varied verb forms. The naming is predictable and aids tool selection.
13 tools is well-scoped for a KPI management server. Each tool covers a necessary aspect (alerts, chapters, members, rubrics, scoring, SLA) without redundancy or bloat. The count feels tailored and purposeful.
The tool set comprehensively covers the KPI domain: alerts, chapter and member metrics, overview, rubrics (both full docs and thresholds), scoring status (coverage and period), member roster, and SLA tracking. For a read-only query server, there are no obvious gaps. All essential read operations are present.