Skip to main content
Glama
Sign In
HAOps MCP Server

HAOps MCP Server

by tbranzov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

haops_export_test_suite

Export a test suite as a JSON bundle to share across projects, including configuration and all test definitions.

Instructions

Export a test suite as a JSON bundle for cross-project sharing. Includes suite config and all test definitions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectSlug": "<projectSlug>",
      "suiteId": "<suiteId>"
    },
    "name": "haops_export_test_suite"
  }
}

Input Schema

NameRequiredDescriptionDefault
suiteIdYesUUID of the test suite to export
projectSlugYesThe project slug (URL identifier)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.0

TDQS

A3.8/5.0
Behavior2/5

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

No annotations provided. Description only states export but does not disclose read-only nature, permissions needed, side effects, or rate limits. For a no-annotation tool, this is insufficient.

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?

Two concise sentences with no wasted words. Front-loaded with verb and resource, then details.

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

Completeness4/5

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

For a simple export tool, description covers what is exported and format. Lacks mention of return format details or error conditions, but adequate given no output schema.

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 has 100% coverage, but description adds value by explaining that the export includes suite config and all test definitions, which is not in parameter descriptions.

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 verb 'Export', resource 'test suite', output format 'JSON bundle', and purpose 'cross-project sharing'. Includes what is bundled, distinguishing from sibling import tool.

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

Usage Guidelines3/5

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

Implies usage for exporting test suites, but no explicit guidance on when to use versus alternatives like import or other export tools. No exclusions or context.

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