Skip to main content
Glama
tbranzov

HAOps MCP Server

by tbranzov

haops_create_project_skill

Create a project-scoped skill visible only to the specified project's protocol resolver, ensuring it is not reusable across other projects.

Instructions

Create a PROJECT-SCOPED skill (POST /api/projects/[slug]/skills). Project-scoped skills are visible only to that project's protocol resolver — they cannot be referenced by system role templates or other projects' protocols. For skills you want reusable across all projects, use haops_create_skill with scope="system" instead.

Admin-only, requires ENABLE_COMPOSED_PROTOCOLS=true. Returns 409 if a non-deleted project skill with the same name already exists in this project — use haops_update_skill(scope="project", projectSlug=...) to publish a new version instead. Returns 404 when the feature flag is off.

Response includes id, scope="project", projectId and version=1.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesKebab-case skill name (1..100 chars, starts with a letter). Must be unique among current (non-deleted) project-scoped skills in this project.
contentYesFull markdown body of the skill (admin-trusted; no sanitization applied server-side).
verboseNoIf true, return the full API response instead of the compact summary (default: false).
categoryYesSkill category for grouping in the catalogue.
spawnLineNoOptional short text injected into the agent spawn-line when this skill is active. Leave unset to use the default spawn-line assembly.
descriptionYesShort one-line description shown in list views and template pickers.
projectSlugYesURL slug of the project this skill belongs to.
applicableRolesYesRoles the skill applies to. Non-empty array of {architect, dev, qa, devops} or the wildcard ["*"].
Behavior4/5

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

With no annotations, the description fully discloses behavior: admin-only requirement, feature flag dependence, conflict handling (409), error when flag off (404), and response structure (id, scope=project, projectId, version=1). Lacks mention of any destructive side effects, but as a create tool this is adequate.

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?

Concise yet complete: single paragraph with clear progression from purpose to scope to alternatives to requirements to errors to response. Every sentence adds unique value.

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

Completeness5/5

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

Given 8 parameters, 6 required, no output schema, and no annotations, the description covers purpose, scope, alternatives, prerequisites, error codes, and response fields. Leaves no critical question unanswered.

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%, so baseline is 3. The description does not add extra meaning to parameters beyond the schema's own descriptions. No additional parameter clarifications provided.

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 creates a project-scoped skill, specifies the API endpoint, explains the scope visibility, and distinguishes it from the system-scoped sibling haops_create_skill.

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

Usage Guidelines5/5

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

Explicitly provides when-to-use (project-scoped), when-not-to-use (use haops_create_skill for system-wide), and alternative tool name. Also outlines prerequisites (admin-only, feature flag) and error scenarios with suggestions.

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