Skip to main content
Glama
jakedx6

Helios-9 MCP Server

by jakedx6

get_workspace_overview

Retrieve a comprehensive workspace overview with analytics and insights. Customize by time range and focus areas like productivity or blockers.

Instructions

Get comprehensive overview of entire workspace with analytics and insights

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
include_analyticsNoWhether to include detailed analytics
time_rangeNoTime range for activity analysisweek
focus_areasNoSpecific areas to focus analysis on

Implementation Reference

  • The main handler function for get_workspace_overview. It parses input (include_analytics, time_range, focus_areas), fetches projects/tasks/documents from supabaseService, and builds an overview with summary stats, project health, productivity metrics, collaboration insights, AI readiness, recommendations, and optional analytics/focused insights.
    export const getWorkspaceOverview = requireAuth(async (args: any) => {
      const { include_analytics, time_range, focus_areas } = GetWorkspaceOverviewSchema.parse(args)
      
      logger.info('Getting workspace overview', { time_range, focus_areas })
    
      // Get all workspace data
      const [projects, tasks, documents] = await Promise.all([
        supabaseService.getProjects({}, { limit: 50 }),
        supabaseService.getTasks({}, { limit: 100 }),
        supabaseService.getDocuments({}, { limit: 100 })
      ])
    
      const overview: any = {
        summary: {
          total_projects: projects.length,
          active_projects: projects.filter(p => p.status === 'active').length,
          total_tasks: tasks.length,
          completed_tasks: tasks.filter(t => t.status === 'done').length,
          total_documents: documents.length,
          documentation_coverage: calculateDocumentationCoverage(projects, documents)
        },
        project_health: analyzeProjectHealth(projects, tasks, documents),
        productivity_metrics: calculateProductivityMetrics(tasks, time_range),
        collaboration_insights: analyzeCollaboration(tasks, documents),
        ai_readiness: assessAIReadiness(documents),
        recommendations: generateWorkspaceRecommendations(projects, tasks, documents)
      }
    
      if (include_analytics) {
        overview.analytics = {
          task_distribution: analyzeTaskDistribution(tasks),
          document_metrics: analyzeDocumentMetrics(documents),
          project_velocity: calculateProjectVelocity(projects, tasks, time_range),
          bottleneck_analysis: identifyBottlenecks(projects, tasks)
        }
      }
    
      if (focus_areas) {
        overview.focused_insights = generateFocusedInsights(overview, focus_areas)
      }
    
      return overview
    })
  • Zod schema (GetWorkspaceOverviewSchema) for validating tool input: include_analytics (boolean, default true), time_range (enum today/week/month/all, default week), focus_areas (optional array of productivity/collaboration/documentation/blockers).
    const GetWorkspaceOverviewSchema = z.object({
      include_analytics: z.boolean().default(true),
      time_range: z.enum(['today', 'week', 'month', 'all']).default('week'),
      focus_areas: z.array(z.enum(['productivity', 'collaboration', 'documentation', 'blockers'])).optional()
    })
  • Tool definition object (getWorkspaceOverviewTool) with name 'get_workspace_overview', description, and JSON Schema inputSchema matching the Zod schema.
    export const getWorkspaceOverviewTool: MCPTool = {
      name: 'get_workspace_overview',
      description: 'Get comprehensive overview of entire workspace with analytics and insights',
      inputSchema: {
        type: 'object',
        properties: {
          include_analytics: {
            type: 'boolean',
            default: true,
            description: 'Whether to include detailed analytics'
          },
          time_range: {
            type: 'string',
            enum: ['today', 'week', 'month', 'all'],
            default: 'week',
            description: 'Time range for activity analysis'
          },
          focus_areas: {
            type: 'array',
            items: {
              type: 'string',
              enum: ['productivity', 'collaboration', 'documentation', 'blockers']
            },
            description: 'Specific areas to focus analysis on'
          }
        }
      }
    }
  • Export map contextAggregationHandlers that maps the string 'get_workspace_overview' to the handler function getWorkspaceOverview, which gets merged into allHandlers in index.ts.
    export const contextAggregationHandlers = {
      get_smart_context: getSmartContext,
      get_workspace_overview: getWorkspaceOverview,
  • src/index.ts:597-602 (registration)
    Resource handler in index.ts that calls allHandlers.get_workspace_overview when the URI path is '/workspace/overview', with default options (include_analytics: true, time_range: 'week').
    // Workspace Resources
    if (path === '/workspace/overview') {
      return await this.allHandlers.get_workspace_overview({
        include_analytics: true,
        time_range: 'week'
      })
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description must carry full burden. It merely states it retrieves an overview, but does not disclose behavioral traits like auth needs, performance implications, or side effects. Minimal transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is a single sentence, concise but borderline terse. It front-loads the purpose, but could be more informative without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, so description should clarify return values. It only mentions 'analytics and insights' but lacks specifics on what the overview contains. For a comprehensive tool with 3 optional parameters, more contextual detail is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so schema already explains parameters well. Description adds no extra meaning beyond what is in the schema, so baseline score of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states verb 'Get', resource 'workspace overview', and scope 'comprehensive with analytics and insights'. However, among siblings like 'get_workspace_context' and 'get_workspace_health', no explicit differentiation is provided.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives, no prerequisites, conditions, or exclusions. Agent receives no help on selection context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jakedx6/helios9-MCP-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server