Skip to main content
Glama
tbranzov

HAOps MCP Server

by tbranzov

haops_discover

Searches documentation metadata to find relevant sections by scope and keywords, returning summaries for quick topic discovery.

Instructions

Metadata-index discovery (ADR-029 P2b): find which doc sections cover a topic BEFORE reading full bodies.

PRIMARY USAGE — filter by scope then pinpoint:

  1. relevantTo (controlled vocab) — SCOPE filter: narrows to sections tagged for your role/task. Roles: architect | dev | qa | devops Task-types: rag | helpdesk | auth | mobile | git | testing | memory | deploy | docs | notifications | livekit | email | distribution | communication Pass one or several values; sections matching ANY value are returned.

  2. q (free text, case-insensitive, forgiving) — PINPOINT filter: searched over title + summary. Combine with relevantTo for best results.

SECONDARY USAGE — exact tag match (brittle, prefer relevantTo): covers — exact agentMetadata.covers tag match (e.g. "auth-and-roles"). Fails silently if tag is misspelled or not yet indexed. Use only when you know the exact tag.

RETURNS thin rows per matching doc section: { entityType, entityId, title, summary, covers, relevantTo, sectionStatus, stale } Feed entityId into haops_get_doc_section to retrieve the full body.

Example — find RAG-related docs scoped to dev role: { projectSlug: "fdev", relevantTo: ["rag", "dev"], q: "metadata index" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFree-text search over title + summary (case-insensitive, max 512 chars). Combine with relevantTo for precision.
limitNoMaximum results to return (1–200, default 25).
coversNoExact agentMetadata.covers tag filter (brittle — fails silently if tag is wrong). Use relevantTo + q instead when possible.
relevantToNoScope filter — controlled vocab: roles (architect/dev/qa/devops) + task-types (rag/helpdesk/auth/mobile/git/testing/memory/deploy/docs/notifications/livekit/email/distribution/communication). Sections matching ANY value are returned.
entityTypesNoEntity types to search. Default: ["doc_section"]. Reserved for future extension.
projectSlugYesThe project slug (URL identifier)
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses that covers fails silently, returns thin rows (not full bodies), and lists returned fields. This is adequate behavioral disclosure for a read tool.

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 sections for primary usage, secondary usage, returns, and example. Front-loaded with purpose. Could be slightly more concise, but it is well-organized and each part 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?

No output schema, but description fully explains return values and how to use them (feed entityId into haops_get_doc_section). Covers main use cases, combination of filters, and example. Complete for a discovery tool.

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%, but description adds significant meaning: controlled vocab for relevantTo (roles and task-types listed), dual-filter strategy, and warning about covers brittleness. This goes beyond the schema.

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 states a specific verb+resource: 'discover' which doc sections cover a topic before reading full bodies. It distinguishes itself from sibling tools like haops_get_doc_section (retrieves full body) and haops_rag_query (likely retrieves content) by emphasizing it returns thin metadata rows.

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

Usage Guidelines4/5

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

Provides explicit guidance: use before reading full bodies, filter by scope (relevantTo) then pinpoint (q). Secondary usage with covers is warned as brittle. Includes an example. While not explicitly listing when not to use, the context is clear.

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