Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

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

Integration testing for event-driven and batch systems. Flows (tests/integration/*.yaml) combine HTTP calls and database checks (shared with k11 API Functional QA) with message steps: listen to a topic BEFORE the action, publish, expect_message / expect_no_message with JSON-path matching, a time limit and optional AsyncAPI schema checks, run_job (a command without a shell, or an HTTP job with polling) and wait_until (poll a SELECT or GET until it holds). Start with integration_config. Publishing and jobs are refused where writes are not allowed and on protected topics; never point flows at production brokers.

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
integration_configC

Brokers, jobs, AsyncAPI contract, protected topics, environments (and whether publishing and jobs may run there) and the flows found under tests/integration/.

run_integration_testsB

Run integration flows (default: all of tests/integration/) and write .qa-mcp/integration-report/ (JSON evidence for the Release Gate, Markdown for the PR, JUnit). Returns the summary and the failing steps with the closest message seen, query results or job output.

validate_flowA

Check a flow file's structure (step kinds and their keys) without running it.

watch_topicA

Listen to a topic for a few seconds (read-only, from now on) and return the messages seen, to learn their shape before writing expect_message steps. Values are shown as sent; don't use it on topics carrying real personal data.

get_reportA

The last integration report, or one flow's steps with full evidence (requests, messages, queries, job output).

init_integration_configB

Write a starter .qa-mcp/integration.yaml and, optionally, tests/integration/example.yaml.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.3/5.0

Scored across 6 tools

Disambiguation4/5

Each tool maps to a distinct phase of the integration-QA workflow (read config, init config, validate a flow, run flows, watch a topic, fetch a report). The only real confusion is between integration_config and init_integration_config, which differ only by an 'init_' prefix, and get_report versus run_integration_tests, which both surface failing-step evidence.

Naming Consistency4/5

Five of six tools use a clean snake_case verb_noun pattern (run_integration_tests, validate_flow, watch_topic, get_report, init_integration_config). integration_config breaks the pattern as a bare noun, but the deviation is minor and readable.

Tool Count5/5

Six tools is well-scoped for a narrow integration-QA/Release-Gate domain, with no obvious filler. Each tool covers a distinct lifecycle step: configure, author, validate, observe, run, and report.

Completeness4/5

The surface covers the full loop from bootstrapping config through validating, running, inspecting, and reporting on flows. The main gap is that there is no way to update or edit an existing integration.yaml (only a one-shot init), forcing agents to rewrite the file blind.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues