Skip to main content
Glama

dev_onboarding_check

Verify developer environment setup by running comprehensive checks to ensure all required tools and configurations are properly installed for DevOps workflows.

Instructions

Run full developer environment check

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'dev_onboarding_check' tool. It checks if Git, GitHub CLI, and Docker are installed and configured properly in the developer's environment, returning a status report.
    export async function devOnboardingCheck() {
      const checks = [];
    
      const gitVersion = await commandRunner("git --version");
      checks.push(gitVersion.success ? `[OK] ${gitVersion.stdout}` : "[FAIL] Git not installed");
    
      const gitConfig = await commandRunner("git config user.name && git config user.email");
      checks.push(gitConfig.success ? `[OK] Git configured: ${gitConfig.stdout.replace("\n", " / ")}` : "[WARN] Git user not configured");
    
      const ghVersion = await commandRunner("gh --version");
      checks.push(ghVersion.success ? `[OK] GitHub CLI: ${ghVersion.stdout.split("\n")[0]}` : "[WARN] GitHub CLI not installed");
    
      const dockerVersion = await commandRunner("docker --version");
      checks.push(dockerVersion.success ? `[OK] ${dockerVersion.stdout}` : "[FAIL] Docker not installed");
    
      const failCount = checks.filter(c => c.startsWith("[FAIL]")).length;
      const warnCount = checks.filter(c => c.startsWith("[WARN]")).length;
    
      let summary = "\n\n";
      if (failCount === 0 && warnCount === 0) {
        summary += "All checks passed! Developer environment is ready.";
      } else {
        summary += `Found ${failCount} critical issues and ${warnCount} warnings.`;
      }
    
      return {
        content: [{
          type: "text",
          text: `DEVELOPER ENVIRONMENT CHECK\n============================\n\n${checks.join("\n\n")}${summary}`
        }]
      };
    }
  • src/tools.js:576-597 (registration)
    The tool 'devOnboardingCheck' (mapped to 'dev_onboarding_check') is registered in the exported 'tools' object, which is likely used by the MCP server to expose all tools.
    export const tools = {
      // Git
      gitStatusExplained,
      gitBranchExplained,
      gitCommitGuided,
      // Docker
      dockerCheckSetup,
      dockerAnalyzeProject,
      dockerBuild,
      // GitHub
      githubSecretsList,
      githubSecretsSet,
      // Azure
      azureCheckCli,
      azureAcrSetup,
      azureContainerAppsDeploy,
      // SonarCloud
      sonarcloudSetupGuide,
      sonarcloudCreateConfig,
      // Onboarding
      devOnboardingCheck,
    };
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Run full developer environment check' implies a diagnostic or validation operation, but it doesn't specify whether it's read-only, if it makes changes, what permissions are needed, or what the output includes. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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, efficient sentence with no wasted words. It's front-loaded with the core action and resource, making it easy to scan. Every word earns its place, achieving optimal conciseness for the given purpose.

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 complexity of a 'full developer environment check' with no annotations, no output schema, and vague purpose, the description is incomplete. It doesn't explain what the check entails, what it returns, or how it differs from sibling tools. For a potentially broad-scope tool, more context is needed to guide effective use.

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 tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately avoids unnecessary details. A baseline of 4 is applied as it handles the lack of parameters efficiently.

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 'Run full developer environment check' states a clear verb ('Run') and resource ('developer environment check'), but it's vague about what constitutes a 'full' check and doesn't distinguish from siblings like 'docker_check_setup' or 'azure_check_cli'. It provides basic purpose but lacks specificity about scope or differentiation.

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?

The description offers no guidance on when to use this tool versus alternatives. With siblings like 'docker_check_setup' and 'azure_check_cli' that might handle specific environment checks, there's no indication of when this comprehensive tool is preferred or what prerequisites exist. Usage is implied but not articulated.

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/rideRTD/RTD-DevOps'

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