Skip to main content
Glama
tbranzov

HAOps MCP Server

by tbranzov

haops_read_protocol

Read the work protocol for a specific agent role in a project, defining scope, workflow, and handoff instructions. Supports lazy loading of skills or bundled full document.

Instructions

Read the work protocol for a specific agent role in a project. Protocols define HOW agents should work (scope, workflow, handoff, etc.).

OUTPUT SHAPES (v2.6 — F4 composed protocols): • Legacy project (templateId IS NULL) — always returns the raw monolithic shape regardless of mode: { mode: "legacy", version, bytes, body, content, ... }. The mode and bundle params have no effect; output is byte-identical to v2.5. • Composed project + mode="lazy" (DEFAULT) — { mode: "composed-lazy", version, bytes, body: "", coreContent, skillRefs[], warnings? }. Agent reads coreContent for the boot section, then uses haops_read_skill to fetch individual skill bodies on demand. • Composed project + mode="bundle" — { mode: "composed-bundle", version, bytes, body, skillRefs[], warnings? }. Full composed markdown in body (template baseBody + each enabled skill body + customContent, joined with "---"). Use this when caching offline or when you need the full document in one round-trip. When version is set, returns that specific historical row (raw DB shape — version history predates composed mode; mode/bundle are ignored).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoF4: how to resolve composed protocols. 'lazy' (default) returns the boot section + skill manifest; agent fetches skill bodies via haops_read_skill. 'bundle' returns the full composed markdown in one shot. Ignored for legacy projects.
roleYesAgent role to read protocol for (e.g., architect, dev, qa, devops)
versionNoSpecific version number to read. If omitted, returns the current version. When set, mode is ignored (historical snapshots are raw DB rows).
projectSlugYesThe project slug (URL identifier)
Behavior5/5

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

Despite no annotations, the description fully discloses output shapes for all scenarios (legacy, composed lazy/bundle, versioned historical), including side effects (e.g., mode ignored for legacy). No contradictions.

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?

Well-structured with front-loaded purpose and organized output shapes section. Slightly verbose but necessary due to complexity.

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?

Covers all edge cases (legacy, composed, historical versions) and explains return shapes despite no output schema. Complete for a complex tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description adds significant behavioral context beyond schema (e.g., how mode affects output, version overriding mode, role semantics). Baseline 3 exceeded.

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?

Clearly states the tool reads the work protocol for a specific agent role in a project, distinguishing it from siblings like haops_read_role_template and haops_read_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 explains when to use lazy vs bundle modes, notes that mode is ignored for legacy projects and version overrides mode, and directs to haops_read_skill for fetching individual skill bodies.

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