Skip to main content
Glama
jakedx6

Helios-9 MCP Server

by jakedx6

get_workspace_context

Retrieve the complete workspace hierarchy and insights to understand project structure, task relationships, and overall team context.

Instructions

Get complete workspace hierarchy and insights

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the get_workspace_context tool. It requires authentication, calls supabaseService.getWorkspaceContext(), and returns the context.
    export const getWorkspaceContext = requireAuth(async (args: any) => {
      logger.info('Getting workspace context')
      
      const context = await supabaseService.getWorkspaceContext()
      
      return { context }
    })
  • The tool definition/schema for get_workspace_context. No input parameters required. Description: 'Get complete workspace hierarchy and insights'.
    export const getWorkspaceContextTool: MCPTool = {
      name: 'get_workspace_context',
      description: 'Get complete workspace hierarchy and insights',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    }
  • Registration of getWorkspaceContextTool in the initiativeTools export object.
    export const initiativeTools = {
      listInitiativesTool,
      getInitiativeTool,
      createInitiativeTool,
      updateInitiativeTool,
      getInitiativeContextTool,
      getInitiativeInsightsTool,
      searchWorkspaceTool,
      getEnhancedProjectContextTool,
      getWorkspaceContextTool,
      associateDocumentWithInitiativeTool,
      disassociateDocumentFromInitiativeTool
    }
  • Registration of getWorkspaceContext handler in the initiativeHandlers map, mapping the tool name 'get_workspace_context' to the handler function.
    export const initiativeHandlers = {
      list_initiatives: listInitiatives,
      get_initiative: getInitiative,
      create_initiative: createInitiative,
      update_initiative: updateInitiative,
      get_initiative_context: getInitiativeContext,
      get_initiative_insights: getInitiativeInsights,
      search_workspace: searchWorkspace,
      get_enhanced_project_context: getEnhancedProjectContext,
      get_workspace_context: getWorkspaceContext,
      associate_document_with_initiative: associateDocumentWithInitiative,
      disassociate_document_from_initiative: disassociateDocumentFromInitiative
    }
  • The API client method that makes the actual HTTP request to '/api/mcp/workspace/context' to fetch workspace context data from the backend.
    async getWorkspaceContext(): Promise<any> {
      const response = await this.request<{ context: any }>('/api/mcp/workspace/context')
      return response.context
    }
Behavior2/5

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

No annotations are present, and the description does not disclose behavioral traits beyond 'get hierarchy and insights'. It does not state that the tool is read-only, require any authentication, or describe what happens if called without context.

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

Conciseness5/5

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

The description is a single sentence, front-loaded, and contains no redundant information. It is efficient and to the point.

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

Completeness3/5

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

Given the tool has no parameters and no output schema, the description is somewhat complete but lacks context to differentiate it from similar sibling tools. An agent may struggle to decide when to use this tool over others.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, so the baseline is 4. The description adds no extra parameter meaning, but there is nothing to add since there are no parameters.

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

Purpose3/5

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

The description 'Get complete workspace hierarchy and insights' clearly states a verb and resource (get workspace context). However, it does not differentiate from sibling tools like 'get_workspace_overview' or 'get_enhanced_project_context', which could have overlapping functionality.

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 is provided on when to use this tool versus alternatives such as 'get_workspace_overview' or 'get_enhanced_project_context'. There is no when-not-to-use or context for selection.

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