Skip to main content
Glama
Sign In
HAOps MCP Server

HAOps MCP Server

by tbranzov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

haops_list_help_articles

List help articles from the project management system. Optionally filter by section slug to find specific documentation.

Instructions

List help articles, optionally filtered by section slug.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "haops_list_help_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionSlugNoFilter articles by section slug (optional, returns all if omitted)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided, and the description does not disclose behavioral traits like pagination, ordering, authentication needs, or that it's read-only. The minimal description leaves uncertainty about side effects and scope.

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 a single sentence with no wasted words. It is front-loaded with the verb 'List' and clearly identifies the resource.

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

Completeness3/5

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

While the tool is simple with one optional parameter, the description lacks details about the return format, pagination, or result set. Without an output schema, the agent relies on the description, which is incomplete.

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 a clear description of the parameter. The tool description simply rephrases the schema, adding no new meaning beyond what is already in 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 clearly states the action 'list help articles' and adds the optional filtering by section slug. It distinguishes from siblings like get_help_article and create_help_article by specifying it's a list operation.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives such as list_help_sections or search_help. No when-not-to-use or context for using the filter optionality.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools