Skip to main content
Glama

init

Initialize OSS Autopilot by setting up your GitHub username to manage open source contributions across repositories.

Instructions

Initialize OSS Autopilot with a GitHub username. Creates the state file and sets up initial configuration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameYesYour GitHub username

Implementation Reference

  • The runInit handler function which updates the githubUsername configuration using the StateManager.
    export async function runInit(options: { username: string }): Promise<InitOutput> {
      validateGitHubUsername(options.username);
      const stateManager = getStateManager();
    
      // Set username in config
      stateManager.updateConfig({ githubUsername: options.username });
    
      return {
        username: options.username,
        message: 'Username saved. Run `daily` to fetch your open PRs from GitHub.',
      };
    }
  • Registration of the 'init' tool in the MCP server, using the runInit handler.
    // 12. init — Initialize with GitHub username
    server.registerTool(
      'init',
      {
        description:
          'Initialize OSS Autopilot with a GitHub username. Creates the state file and sets up initial configuration.',
        inputSchema: {
          username: z.string().describe('Your GitHub username'),
        },
        annotations: { readOnlyHint: false, destructiveHint: false },
      },
      wrapTool(runInit),
    );
  • Type definition for the output of the init command.
    export interface InitOutput {
      username: string;
      message: string;
    }
Behavior3/5

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

Annotations indicate writing (readOnlyHint: false) but not destructive behavior. The description adds value by specifying what gets created (state file, initial configuration), confirming the write operation, but lacks details on side effects, error conditions, or overwrite behavior.

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?

Two efficient sentences with zero waste. Front-loaded with the action (Initialize), followed by the parameter requirement, then the effects (creates state file, sets up config). Every word earns its place.

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

Completeness4/5

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

Appropriately complete for a simple initialization tool with one well-documented parameter. With annotations covering safety profile and schema covering inputs, the description covers the essential behavioral context (file creation). Minor gap regarding idempotency or existing-state handling prevents a 5.

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 coverage is 100% with the username parameter fully documented as 'Your GitHub username'. The description mentions 'with a GitHub username' but does not add semantic details (format validation, case sensitivity) beyond what the schema already provides. Baseline 3 appropriate for high-coverage schemas.

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?

Clear verb (Initialize) and resource (OSS Autopilot), and mentions specific artifacts created (state file, configuration). However, it does not explicitly distinguish from sibling tools like 'setup', 'startup', or 'check-setup' which appear to have overlapping lifecycle concerns.

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?

States what the tool does but provides no guidance on when to use it versus alternatives like 'setup' or 'startup', nor does it indicate prerequisites or idempotency (e.g., whether it can safely be run multiple times).

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