# Archived: Low-Value Analytics Tools
**Date Archived:** 2025-01-14
**Reason:** Low business value - generic analytics that can be replaced with direct queries
## What Was Archived
10 analytics tools that provide generic business intelligence without JobNimbus-specific value:
### Communication & Conversion Analytics (5 tools)
1. **get_communication_analytics**
- **Why Archived:** Generic call/email/text tracking not specific to JobNimbus workflows
- **Replacement:** Use `get_activities` with filtering + basic aggregation
- **Usage Pattern:** Rarely used, data available through native activities endpoint
2. **get_conversion_funnel_analytics**
- **Why Archived:** Multi-stage funnel analysis too generic, not JobNimbus-specific
- **Replacement:** Use `search_jobs` with status filters + count aggregation
- **Usage Pattern:** Can be built from job status transitions
3. **get_resource_allocation_analytics**
- **Why Archived:** Team resource distribution not specific to construction/roofing industry
- **Replacement:** Use `get_users` + `get_tasks` + basic capacity calculations
- **Usage Pattern:** Generic HR analytics, not JobNimbus core value
4. **get_customer_satisfaction_analytics**
- **Why Archived:** NPS and satisfaction scoring not native to JobNimbus data
- **Replacement:** External survey tools or manual tracking
- **Usage Pattern:** Requires external data sources JobNimbus doesn't provide
5. **get_time_tracking_analytics**
- **Why Archived:** Billable hours tracking not JobNimbus's primary use case
- **Replacement:** Use `get_activities` with duration calculations
- **Usage Pattern:** Time tracking better served by dedicated time tracking tools
### Project & Operations Analytics (5 tools)
1. **get_project_management_analytics**
- **Why Archived:** Generic project milestones not specific to construction jobs
- **Replacement:** Use `get_jobs` + `get_activities` + status tracking
- **Usage Pattern:** Too broad, overlaps with existing job tracking
2. **get_marketing_campaign_analytics**
- **Why Archived:** Lead source ROI tracking not JobNimbus's core value proposition
- **Replacement:** Use `search_jobs` with source filters + revenue aggregation
- **Usage Pattern:** Marketing analytics better served by dedicated marketing tools
3. **get_financial_forecasting_analytics**
- **Why Archived:** Generic revenue predictions using basic formulas
- **Replacement:** Use `get_profitability_dashboard` (kept - high value) or external BI tools
- **Usage Pattern:** Forecasting needs sophisticated external tools
4. **get_customer_segmentation_analytics**
- **Why Archived:** RFM analysis and clustering not construction-industry specific
- **Replacement:** Use `get_contacts` + `get_jobs` + external segmentation tools
- **Usage Pattern:** Customer segmentation better served by CRM platforms
5. **get_operational_efficiency_analytics**
- **Why Archived:** Generic process efficiency metrics, too broad
- **Replacement:** Use industry-specific tools like `analyze_insurance_pipeline` (kept)
- **Usage Pattern:** Vague metrics without actionable JobNimbus-specific insights
## Why These Were Low-Value
All 10 tools share these characteristics:
| Issue | Description |
|-------|-------------|
| **Generic Business Logic** | No JobNimbus-specific intelligence or construction industry focus |
| **External Data Required** | Rely on data not available in JobNimbus (NPS scores, time tracking, etc.) |
| **Replaceable with Queries** | All functionality achievable with native API endpoints + basic aggregation |
| **Low Adoption** | Rarely used compared to high-value tools like insurance/retail pipelines |
| **Maintenance Overhead** | Complex calculations with little ROI |
## Better Alternatives
Instead of these 10 generic tools, use:
### **KEPT: High-Value Analytics (25 tools remaining)**
**Insurance & Retail Pipelines (3 tools) - INDUSTRY-SPECIFIC:**
- `analyze_insurance_pipeline` - Claims, adjusters, negotiation analytics
- `analyze_retail_pipeline` - Conversions, financing, payment tracking
- `analyze_services_repair_pipeline` - Service time, technician efficiency
**Financial Analytics (7 tools) - JOBNIMBUS-FOCUSED:**
- `get_sales_rep_performance` - Rep metrics with accurate financials
- `get_performance_metrics` - Comprehensive KPI dashboard
- `get_automated_followup` - Smart scheduling
- `get_revenue_report` - Revenue analysis by period
- `get_margin_analysis` - Profit margins by job type/rep
- `analyze_revenue_leakage` - Identify revenue loss points
- `get_profitability_dashboard` - Real-time profitability KPIs
**Performance & Forecasting (2 tools) - CONSTRUCTION-SPECIFIC:**
- `get_seasonal_trends` - Seasonal demand with roofing/construction focus
- `get_pipeline_forecasting` - Quarterly revenue predictions
**Job & Territory Analytics (8 tools) - FIELD-OPERATIONS:**
- `get_job_summary` - Job analytics dashboard
- `get_optimal_door_routes` - Door-to-door sales route optimization
- `get_territory_heat_maps` - Geographic performance analysis
- `get_activities_analytics` - Productivity metrics
- `get_jobs_distribution` - Geographic distribution
- `get_door_knocking_scripts_by_area` - Area-specific sales scripts
- `get_seasonal_door_timing` - Optimal timing for door sales
- `get_estimates_with_addresses` - Geographic estimate mapping
**Task & User Productivity (3 tools) - JOBNIMBUS-NATIVE:**
- `get_task_management_analytics` - Priority tracking, completion metrics
- `get_user_productivity_analytics` - Team performance analysis
- `get_lead_scoring_analytics` - AI-powered lead qualification
**Sales & Competition (2 tools) - SALES-FOCUSED:**
- `get_sales_velocity_analytics` - Win rates, sales cycle duration
- `get_competitive_analysis_analytics` - Win/loss analysis
### **Direct API Alternatives**
Instead of archived tools, use native endpoints:
```typescript
// Instead of: get_communication_analytics()
// Use: get_activities(activity_type="Call")
// Instead of: get_conversion_funnel_analytics()
// Use: search_jobs_by_status() for each stage + count
// Instead of: get_resource_allocation_analytics()
// Use: get_users() + get_tasks(assignee_filter=user_id)
// Instead of: get_customer_satisfaction_analytics()
// Use: External survey platform (SurveyMonkey, Typeform)
// Instead of: get_time_tracking_analytics()
// Use: get_activities() + duration field aggregation
// Instead of: get_project_management_analytics()
// Use: get_jobs() + get_activities() + status tracking
// Instead of: get_marketing_campaign_analytics()
// Use: search_jobs(source_filter=campaign) + revenue sum
// Instead of: get_financial_forecasting_analytics()
// Use: get_profitability_dashboard() or external BI tools
// Instead of: get_customer_segmentation_analytics()
// Use: get_contacts() + get_jobs(customer_id) + external CRM
// Instead of: get_operational_efficiency_analytics()
// Use: analyze_insurance_pipeline() (construction-specific)
```
## Impact of Removal
**Token Efficiency:**
- 10 fewer tools in MCP tool listing
- ~1,000-1,500 tokens saved per request
- Faster AI tool selection (fewer options to evaluate)
**Maintenance:**
- Removed 10 complex tools with low ROI
- Focused on 25 high-value, industry-specific analytics
- Clearer value proposition for JobNimbus MCP integration
**User Experience:**
- Less confusion from generic tools
- Clearer focus on construction/roofing industry needs
- Better alternatives highlighted
## Restoration
If these tools are needed in the future, the files are preserved in this directory:
- `getCommunicationAnalytics.ts`
- `getConversionFunnelAnalytics.ts`
- `getResourceAllocationAnalytics.ts`
- `getCustomerSatisfactionAnalytics.ts`
- `getTimeTrackingAnalytics.ts`
- `getProjectManagementAnalytics.ts`
- `getMarketingCampaignAnalytics.ts`
- `getFinancialForecastingAnalytics.ts`
- `getCustomerSegmentationAnalytics.ts`
- `getOperationalEfficiencyAnalytics.ts`
To restore:
1. Move files back to `src/tools/analytics/`
2. Add imports back to `src/tools/index.ts`
3. Register tools in the ToolRegistry constructor
4. Rebuild and deploy
**Note:** Before restoring, consider:
- Are there better alternatives in the remaining 25 analytics tools?
- Can this be achieved with native API endpoints + basic aggregation?
- Is this JobNimbus-specific or generic business intelligence?
## Related Changes
- **Phase 2 Part 1 of MCP Tools Optimization Plan**
- **Previous:** Phase 1 reduced 103 → 89 tools (quick status consolidation + redundant removal)
- **This change:** Archive 10 low-value analytics tools (89 → 79 tools)
- **Next:** Consolidate 10 territory/job analytics → 4 tools (Phase 2 Part 2)
- **See:** `MCP_Tools_Optimization_Plan.html` for full context
## Philosophy
**Keep:**
- Construction/roofing industry-specific analytics
- JobNimbus workflow-focused tools
- Tools that provide unique value not available through native API
**Archive:**
- Generic business intelligence available in other platforms
- Tools requiring external data not in JobNimbus
- Analytics replaceable with simple API queries + aggregation
**Result:**
Focus on what makes JobNimbus MCP valuable: **construction industry intelligence**, not generic BI.
