Skip to main content
Glama
jakedx6

Helios-9 MCP Server

by jakedx6

get_initiative_context

Retrieve in-depth context about an initiative, including its place in the project hierarchy and associated documents, for AI-powered project management.

Instructions

Get rich context about an initiative for AI understanding

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
initiative_idYesThe unique identifier of the initiative

Implementation Reference

  • The getInitiativeContext handler function that executes the tool logic. It parses the initiative_id from args using GetInitiativeSchema, logs the request, calls supabaseService.getInitiativeContext(initiative_id), and returns {context}.
    export const getInitiativeContext = requireAuth(async (args: any) => {
      const { initiative_id } = GetInitiativeSchema.parse(args)
      
      logger.info('Getting initiative context for AI', { initiative_id })
      
      const context = await supabaseService.getInitiativeContext(initiative_id)
      
      return { context }
    })
  • Tool registration/definition with name 'get_initiative_context', description, and inputSchema requiring initiative_id (UUID format).
    export const getInitiativeContextTool: MCPTool = {
      name: 'get_initiative_context',
      description: 'Get rich context about an initiative for AI understanding',
      inputSchema: {
        type: 'object',
        properties: {
          initiative_id: {
            type: 'string',
            format: 'uuid',
            description: 'The unique identifier of the initiative'
          }
        },
        required: ['initiative_id']
      }
    }
  • The GetInitiativeSchema Zod schema used for input validation. It validates that initiative_id is a UUID string. This schema is shared with the getInitiative handler.
    const GetInitiativeSchema = z.object({
      initiative_id: z.string().uuid()
    })
  • Registration of getInitiativeContext under the 'get_initiative_context' key in the initiativeHandlers object, which gets merged into allHandlers in src/index.ts.
    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 SupabaseService.getInitiativeContext method that makes an API request to /api/mcp/initiatives/${initiativeId}/context and returns the context data.
    async getInitiativeContext(initiativeId: string): Promise<any> {
      const response = await this.request<{ context: any }>(`/api/mcp/initiatives/${initiativeId}/context`)
      return response.context
    }
Behavior2/5

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

With no annotations, the description must disclose behavioral traits, but it only offers 'rich context' without specifying what data is returned, any side effects, or required permissions. This is insufficient for an agent to understand the tool's behavior.

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?

The description is a single sentence, which is concise, but it lacks specific details that would make it informative. It is not efficiently front-loaded with actionable information.

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?

Given the absence of an output schema, the description should explain what the tool returns, but it does not. The tool is simple, but the description is too vague to be complete.

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?

The input schema has 100% description coverage, and the parameter 'initiative_id' is adequately defined. The description adds no additional semantics beyond the schema, so a baseline score of 3 is appropriate.

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?

The description clearly states the verb 'Get' and resource 'initiative context', indicating a retrieval operation. However, it does not differentiate from siblings like get_initiative_insights or get_smart_context, making the purpose somewhat ambiguous.

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. There is no mention of context, prerequisites, or when not to use it.

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