Skip to main content
Glama
tbranzov

HAOps MCP Server

by tbranzov

haops_preview_project_protocol

Preview project protocol without persisting changes. Verify that template and skill configurations resolve correctly before applying updates.

Instructions

Dry-run the composed-protocol resolver for a project role — returns the assembled manifest as if PUT had been applied, WITHOUT persisting. Use BEFORE haops_update_protocol to verify that the new templateId / skillsConfig combo resolves correctly and has no warnings.

When called with no optional params, previews the current protocol settings (useful for a sanity-check without triggering a version bump).

The response shape mirrors haops_read_protocol (mode, coreContent/body, skillRefs, warnings). The server adds preview: true to distinguish the response from a real read.

Requires ENABLE_COMPOSED_PROTOCOLS=true on the server. Returns 404 when the feature flag is off (the route looks absent, by design) — surface this as "Composed protocols feature is disabled" to the user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rawNoIf true, return the raw JSON envelope verbatim instead of the formatted text summary (default: false).
roleYesAgent role to resolve the protocol for.
templateIdNoOptional. UUID of the role template to resolve against. When omitted, the project's current templateId is used.
projectSlugYesURL slug of the target project (e.g. "fdev", "knf").
customContentNoOptional. Custom markdown appended after the template body. Leave unset to use the project's current customContent.
enabledSkillIdsNoOptional. UUIDs of skills to enable in the preview (merged with template defaults). Leave unset to use the project's current enabledSkillIds.
disabledSkillIdsNoOptional. UUIDs of skills to disable in the preview. Leave unset to use the project's current disabledSkillIds.
Behavior5/5

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

No annotations provided, so description carries full burden: clearly states it's non-persisting, describes response shape with preview flag, and documents the feature flag dependency and 404 behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Five sentences efficiently cover purpose, usage, and behavior; front-loaded with key guidance. Slightly verbose but every sentence earns its place.

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?

Despite no output schema, the description specifies the response shape (mirrors haops_read_protocol with preview flag) and covers all essential aspects for correct usage, including error handling.

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?

Schema coverage is 100%, baseline 3. Description adds value by explaining parameter defaults (e.g., 'leave unset to use project's current') and links them to the preview context, though the enum for role is already self-explanatory.

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 as a dry-run preview for composing protocol, explicitly distinguishes from haops_update_protocol and haops_read_protocol by contrasting persistence vs non-persistence.

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 advises to use BEFORE haops_update_protocol to verify resolution and warnings, and explains the behavior when no optional params are provided. Also notes the server feature flag requirement and the 404 response when disabled.

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