Skip to main content
Glama
tbranzov

HAOps MCP Server

by tbranzov

haops_generate_onboarding

Generate a Developer Onboarding Kit ZIP file with pre-configured workspace, agent definitions, and project settings for a new developer. Saves the ZIP locally and returns the file path.

Instructions

Generate a Developer Onboarding Kit (ZIP) for a new developer joining a project. Creates pre-configured agent workspace with memory files, agent definitions, and project configuration. The ZIP is saved to a local temp file and the file path is returned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
osNoServer OS (e.g. "Ubuntu 22.04") (optional)
ormYesORM/query library (e.g. "Sequelize", "Prisma", "ActiveRecord")
appPathNoApplication path on production server (optional)
repoUrlNoGit repository URL (optional)
sshUserNoSSH user for production server (optional)
databaseYesDatabase system (e.g. "PostgreSQL", "MySQL", "MongoDB")
languageNoLanguage for generated docs (default: "English")
repoPathYesLocal repository path (e.g. "~/Projects/my-app")
dbNameDevYesDevelopment database name
dbUserDevYesDevelopment database user
frameworkYesProject framework (e.g. "Next.js", "Django", "Rails")
outputDirNoDirectory to save the ZIP file (default: /tmp)
publicUrlNoPublic URL of the deployed app (optional)
sshMethodNoSSH auth method: "key" or "password" (optional)
webServerNoWeb server (e.g. "Nginx", "Apache") (optional)
serverHostNoProduction server hostname (optional)
testRunnerNoTest runner command (e.g. "npm test") (optional)
haopsApiKeyNoExisting HAOps API key to include in the kit (optional)
projectSlugYesThe project slug (URL identifier)
uiFrameworkYesUI framework (e.g. "MUI", "Tailwind", "Bootstrap")
devServerUrlYesLocal dev server URL (e.g. "http://localhost:3000")
dbPasswordDevNoDevelopment database password (optional)
developerNameYesFull name of the developer being onboarded
testFrameworkNoTest framework (e.g. "Jest", "Pytest") (optional)
developerEmailYesEmail of the developer being onboarded
generateApiKeyNoGenerate a new HAOps API key for the developer (default: false)
processManagerNoProcess manager (e.g. "PM2", "systemd") (optional)
screenshotScriptNoScreenshot script path (optional)
programmingLanguageYesPrimary programming language (e.g. "TypeScript", "Python", "Ruby")
Behavior3/5

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

The description discloses that the ZIP is saved to a local temp file and returns a path, but it does not cover side effects (e.g., overwrites, auth requirements) or behavior beyond basic output. With no annotations, more behavioral detail would be helpful.

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 three sentences, front-loaded with the key purpose, and contains no fluff. Every sentence adds value.

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?

Given the high parameter count (29) and absence of output schema, the description adequately explains the output and purpose. It could be improved by mentioning error conditions or required permissions, but is fairly complete for its complexity.

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 all parameters described. The description adds no extra meaning beyond what the schema already provides, so baseline score is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool generates a Developer Onboarding Kit ZIP, listing specific contents (memory files, agent definitions, project configuration). It distinguishes this from other sibling CRUD tools by focusing on generation rather than management.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is for onboarding new developers but does not specify when to use it versus alternatives, nor does it mention prerequisites or when not to use it. Usage is implied by context but not explicit.

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/tbranzov/haops-mcp-server'

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