Skip to main content
Glama
jakedx6

Helios-9 MCP Server

by jakedx6

debug_environment

Inspect and debug the MCP server's environment and configuration to identify setup issues.

Instructions

Debug tool to check MCP server environment and configuration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the debug_environment tool. Reads environment variables (HELIOS_API_URL, HELIOS_API_KEY, NODE_ENV, etc.), optionally performs a test API call to verify connectivity, and returns environment info, API test result, and timestamp.
    export const debugEnvironment = async (args: any) => {
      logger.info('Debug environment called')
      
      const envInfo = {
        HELIOS_API_URL: process.env.HELIOS_API_URL || 'NOT SET',
        HELIOS_API_KEY_PREFIX: process.env.HELIOS_API_KEY ? 
          process.env.HELIOS_API_KEY.substring(0, 20) + '...' : 'NOT SET',
        HELIOS_API_KEY_LENGTH: process.env.HELIOS_API_KEY?.length || 0,
        NODE_ENV: process.env.NODE_ENV || 'NOT SET',
        CWD: process.cwd(),
        NODE_VERSION: process.version,
      }
      
      // Try a direct API call
      let apiTestResult = 'Not tested'
      if (process.env.HELIOS_API_URL && process.env.HELIOS_API_KEY) {
        try {
          const response = await fetch(`${process.env.HELIOS_API_URL}/api/mcp/projects?limit=1`, {
            headers: {
              'Authorization': `Bearer ${process.env.HELIOS_API_KEY}`,
              'Content-Type': 'application/json'
            }
          })
          apiTestResult = `${response.status} ${response.statusText}`
          if (response.ok) {
            const data = await response.json()
            apiTestResult += ` - ${data.projects?.length || 0} projects found`
          }
        } catch (error) {
          apiTestResult = `Error: ${error instanceof Error ? error.message : String(error)}`
        }
      }
      
      return {
        environment: envInfo,
        apiTest: apiTestResult,
        timestamp: new Date().toISOString()
      }
    }
  • Tool definition with name 'debug_environment', description, and empty input schema (no parameters required).
    export const debugEnvironmentTool: MCPTool = {
      name: 'debug_environment',
      description: 'Debug tool to check MCP server environment and configuration',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    }
  • src/index.ts:27-27 (registration)
    Import of debugTools and debugHandlers from the debug.ts module into the main server.
    import { debugTools, debugHandlers } from './tools/debug.js'
  • src/index.ts:128-141 (registration)
    Registration of all debug tools (including debugEnvironmentTool) into the server's allTools array for listing via ListToolsRequestSchema.
    // Combine all tools and handlers
    this.allTools = [
      ...Object.values(projectTools),
      ...Object.values(taskTools),
      ...Object.values(documentTools),
      ...Object.values(conversationTools),
      ...Object.values(contextAggregationTools),
      ...Object.values(workflowAutomationTools),
      ...Object.values(intelligentSearchTools),
      ...Object.values(analyticsInsightsTools),
      ...Object.values(initiativeTools),
      ...promptToProjectTools,
      ...Object.values(debugTools),
    ]
  • src/index.ts:143-155 (registration)
    Registration of debug_environment handler in the allHandlers map. When CallToolRequestSchema receives a call with name 'debug_environment', it dispatches to this handler.
    this.allHandlers = {
      ...projectHandlers,
      ...taskHandlers,
      ...documentHandlers,
      ...conversationHandlers,
      ...contextAggregationHandlers,
      ...workflowAutomationHandlers,
      ...intelligentSearchHandlers,
      ...analyticsInsightsHandlers,
      ...initiativeHandlers,
      ...promptToProjectTools.reduce((acc, tool) => ({ ...acc, [tool.name]: tool.handler }), {}),
      ...debugHandlers,
    }
Behavior2/5

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

No annotations provided, and the description only says 'debug tool to check'. It does not disclose whether the operation is read-only, what side effects (if any) occur, or what environment information is returned. Minimal behavioral transparency.

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, clear sentence with no wasted words. It is front-loaded and efficiently communicates the tool's purpose.

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?

For a simple debug tool with no output schema or annotations, the description is minimally adequate. It names the tool's function but lacks details on what exactly is checked or how results are presented.

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?

There are no parameters, so the description adds no extra meaning beyond the empty schema. Per guidelines, 0 parameters yields a baseline score of 4.

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 it is a debug tool for checking MCP server environment and configuration. It is specific and distinct from the sibling tools, which focus on analysis, initiatives, and searches.

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 explicit guidance on when to use this tool versus alternatives. The description implies it is for debugging, but lacks context about prerequisites or situations where other tools would be more appropriate.

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