Skip to main content
Glama

startup

Verify GitHub authentication, validate state files, and check configuration status to ensure the open source contribution manager is ready for use.

Instructions

Run startup checks including GitHub auth verification, state file validation, and configuration status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler for the 'startup' command. It performs setup checks, auth verification, daily digest updates, and initiates the dashboard server.
    export async function runStartup(): Promise<StartupOutput> {
      const version = getCLIVersion();
      const stateManager = getStateManager();
    
      // 1. Check setup — auto-detect if incomplete
      let autoDetected = false;
      if (!stateManager.isSetupComplete()) {
        const detectedUsername = await detectGitHubUsername();
        if (detectedUsername) {
          try {
            stateManager.initializeWithDefaults(detectedUsername);
            autoDetected = true;
          } catch (err) {
            console.error(
              `[STARTUP] Auto-detected username "${detectedUsername}" but failed to save config:`,
              errorMessage(err),
            );
            return { version, setupComplete: false };
          }
        } else {
          return { version, setupComplete: false };
        }
      }
    
      // 2. Check auth
      const token = getGitHubToken();
      if (!token) {
        return {
          version,
          setupComplete: true,
          authError:
            'GitHub authentication required. Install GitHub CLI (https://cli.github.com/) and run "gh auth login", or set GITHUB_TOKEN.',
        };
      }
    
      // 3. Run daily check
      const daily = await executeDailyCheck(token);
    
      // 4. Launch interactive SPA dashboard
      // Skip opening on first run (0 PRs) — the welcome flow handles onboarding
      let dashboardUrl: string | undefined;
      let dashboardOpened = false;
    
      if (daily.digest.summary.totalActivePRs > 0) {
        try {
          const spaResult = await launchDashboardServer();
          if (spaResult) {
            dashboardUrl = spaResult.url;
            openInBrowser(spaResult.url);
            dashboardOpened = true;
          } else {
            console.error('[STARTUP] Dashboard SPA assets not found. Build with: cd packages/dashboard && pnpm run build');
          }
        } catch (error) {
          console.error('[STARTUP] SPA dashboard launch failed:', errorMessage(error));
        }
      }
    
      // Append dashboard status to brief summary (only startup opens the browser, not daily)
      if (dashboardOpened) {
        daily.briefSummary += ' | Dashboard opened in browser';
      }
    
      // 5. Detect issue list
      const issueList = detectIssueList();
    
      return {
        version,
        setupComplete: true,
        autoDetected,
        daily,
        dashboardUrl,
        issueList,
      };
    }
  • MCP tool registration for 'startup' which wraps the 'runStartup' handler.
    // 15. startup — Run startup checks
    server.registerTool(
      'startup',
      {
        description:
          'Run startup checks including GitHub auth verification, state file validation, and configuration status.',
        inputSchema: {},
        annotations: { readOnlyHint: false, destructiveHint: false },
      },
      wrapTool(runStartup),
Behavior2/5

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

Annotations indicate readOnlyHint=false (suggests state mutation), yet the description frames everything as 'checks' which implies read-only validation. It fails to disclose what gets modified during these checks (e.g., logs written, timestamps updated) or what happens when verification fails.

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?

Single sentence that is front-loaded with the action verb and efficiently enumerates the three verification categories without redundancy. Zero waste.

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?

Adequate for a zero-parameter tool with annotations covering the safety profile, but lacks expected details about return values, failure modes, or side effects given that readOnlyHint=false suggests state mutation.

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?

Zero parameters present in the schema, which establishes the baseline score per rubric. No parameter semantics are needed or provided in the description.

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?

Clearly identifies the specific operations performed (GitHub auth verification, state file validation, configuration status) with a specific verb 'Run'. However, it does not clarify how this differs from similar sibling tools like 'check-setup' or 'init'.

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?

Lists what the tool checks but provides no guidance on when to invoke it (e.g., on server startup vs manually) or when to use alternatives like 'check-setup' or 'init' instead.

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/costajohnt/oss-autopilot'

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