Skip to main content
Glama
gabriel-tbc

qa-toolkit-mcp

by gabriel-tbc

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
QA_TOOLKIT_RUNS_DIRNoPath to the folder containing test run reports. Defaults to './runs/'../runs/

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
qa_list_runsA

List available test runs from the configured runs directory.

Returns metadata only (run_id, suite, timestamps, counts) — not the full
list of test cases. Use `qa_get_run` for that.

Filters are applied in this order: suite (exact match), since, until.
Results are sorted by `started_at` ascending. Pagination via limit/offset.

Returns:
    Markdown table or JSON depending on response_format. JSON shape:
    {
        "total": int,
        "count": int,
        "offset": int,
        "has_more": bool,
        "next_offset": int | null,
        "items": [
            {"run_id": str, "suite": str, "started_at": iso8601,
             "summary": {"total","passed","failed","skipped","errors"}}
        ]
    }

Error response: string starting with "Error:".
qa_get_runA

Return a single test run by id.

By default, only failed/error tests are listed in the body (to keep context
small). Set `include_passed=true` for the full inventory.

Returns:
    Markdown or JSON depending on response_format. JSON returns the full
    RunReport model conforming to schemas/run-report.v1.json.

Error response: string starting with "Error: ..." (e.g., "Error: Run not found").
qa_compare_runsA

Compare two test runs and categorize the differences.

`run_a` is treated as baseline (older), `run_b` as newer.

Categories returned:
    regressions          passed in A, failed/error in B (highest priority)
    fixes                failed/error in A, passed in B
    persistent_failures  failed in both
        same_error       fingerprints match → same root cause
        different_error  fingerprints differ → root cause changed
    new_tests            in B but not A
    removed_tests        in A but not B
    other_changes        transitions involving skipped (low priority)

Flakiness detection requires N>2 runs and is not in this tool. Use the
weekly_regression_review prompt to orchestrate multi-run analysis.

Returns:
    Markdown summary or JSON of the full ComparisonResult model.

Error response: string starting with "Error: ...".

Prompts

Interactive templates invoked by user choice

NameDescription
weekly_regression_reviewSlash command: end-of-week regression review. The host injects this as a user message. The model is expected to use qa_list_runs / qa_get_run / qa_compare_runs to fulfill it. Args: suite: Optional suite filter (e.g., "api-regression"). Empty = all suites. days: How many days back to consider. Default 7.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 3 tools

Disambiguation5/5

The three tools have clearly distinct purposes: listing runs, getting a single run's details, and comparing two runs. There is no overlap or ambiguity.

Naming Consistency5/5

All tool names follow the consistent pattern 'qa_<verb>_runs' (list_runs, get_run, compare_runs), using snake_case and a clear verb_noun structure.

Tool Count4/5

Three tools is on the lower end but still reasonable for a focused test run analysis toolkit. The count matches the scope of listing, retrieving, and comparing runs.

Completeness3/5

The set covers the core operations of browsing and comparing test runs, but it lacks tools for creating, updating, or deleting runs, and flakiness detection is explicitly omitted. There are notable gaps for full lifecycle management.

Maintenance

ActivityInactive
ResponsivenessNo issues