HAOps MCP Server

haops_report_test_run

Report test results to HAOps by creating a TestRun with individual TestResult records, enabling manual result submission for agents.

Instructions

Report test results to HAOps. Creates a TestRun with individual TestResult records. Used by agents to manually report results (Jest/Playwright reporters do this automatically).

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>",
      "runner": "<runner>",
      "summary": "<summary>",
      "results": "<results>"
    },
    "name": "haops_report_test_run"
  }
}

Input Schema

Name	Required	Description
`branch`	No	Git branch name (optional)
`runner`	Yes	Test runner that produced results
`results`	Yes	Individual test results
`summary`	Yes	Summary counts
`verbose`	No	If true, return the full API response instead of the compact summary (default: false)
`coverage`	No	Coverage percentages (optional)
`commitSha`	No	Git commit SHA (optional)
`environment`	No	Environment where tests ran (optional)
`projectSlug`	Yes	The project slug (URL identifier)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.8.0Jul 7, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description bears full burden. It discloses the creation behavior (creating TestRun and TestResult records) but lacks details on side effects, idempotency, authentication, or error states. It is adequate but not rich.

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 two sentences, front-loaded with purpose, and contains no unnecessary words. Each sentence adds value.

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

Completeness2/5

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

Given the tool's complexity (9 parameters, nested objects, no output schema), the description is insufficient. It doesn't explain return values or how summary/results relate, and lacks details on behavior like overwriting or partial failures.

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%, so baseline is 3. The description adds no extra meaning beyond the schema; it summarizes the action but doesn't clarify parameter relationships or defaults. It does not compensate for any gaps.

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 reports test results to HAOps by creating a TestRun with TestResult records. It uses specific verbs and resources, and the mention of manual vs automatic reporting distinguishes it from sibling tools like haops_list_test_runs.

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?

The description explicitly says it is 'Used by agents to manually report results,' contrasting with automatic reporters like Jest/Playwright. This gives clear when-to-use guidance, though it doesn't explicitly state when not to use it or list alternative tools.

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

Deploy Server