QA Orchestrator

Overview Schema Source Related Servers Discussions Admin

Discover QA profiles and bundles

get_qa_orchestration_catalog

Read-onlyIdempotent

Read the static catalog of QA specialists, review scopes, and execution schedules before creating a session or choosing a triage route; no arguments required.

Instructions

Read the static profile/bundle catalog: specialists, review scopes, and execution schedules.

Use before creating a session or choosing its triage route; no session or arguments required. Task-type recommendations are shortlists, not restrictions. Choose a bundle for broad work or a single profile for a narrow concern using changed files and confirmed stack.

For a session, the successful triage response includes selected_review_routes with the selected profile or bundle checklists and execution_groups.
Standalone or recovery lookup: prepare_qa_orchestration(agent_profile) or prepare_qa_orchestration_bundle(bundle).
Create a session: start_qa_orchestration; set its route: advance_qa_orchestration.
Session IDs: list_qa_orchestrations().

Available routes come from the installed server's bundled definitions; active sessions and configured models do not change this catalog.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`bundles`	Yes
`profiles`	Yes
`read_only`	No
`host_owns_decisions`	No
`recommended_bundles_by_task_type`	Yes	Task-based shortlists only; they do not restrict the available bundles.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.2.20Oct 29, 2026

changedOutput schema / properties / bundles / items / properties / execution_groups / items / items / enum

Previous value: -[
-  "pr_test_analyzer",
-  "code_reviewer",
-  "security_reviewer",
-  "silent_failure_hunter",
-  "code_explorer",
-  "typescript_reviewer",
-  "react_reviewer",
-  "ruby_reviewer",
-  "python_reviewer",
-  "mobile_reviewer",
-  "omission_auditor"
-]New value: +[
+  "pr_test_analyzer",
+  "code_reviewer",
+  "security_reviewer",
+  "silent_failure_hunter",
+  "code_explorer",
+  "typescript_reviewer",
+  "react_reviewer",
+  "ruby_reviewer",
+  "python_reviewer",
+  "mobile_reviewer"
+]

changedOutput schema / properties / bundles / items / properties / profiles / items / enum

Previous value: -[
-  "pr_test_analyzer",
-  "code_reviewer",
-  "security_reviewer",
-  "silent_failure_hunter",
-  "code_explorer",
-  "typescript_reviewer",
-  "react_reviewer",
-  "ruby_reviewer",
-  "python_reviewer",
-  "mobile_reviewer",
-  "omission_auditor"
-]New value: +[
+  "pr_test_analyzer",
+  "code_reviewer",
+  "security_reviewer",
+  "silent_failure_hunter",
+  "code_explorer",
+  "typescript_reviewer",
+  "react_reviewer",
+  "ruby_reviewer",
+  "python_reviewer",
+  "mobile_reviewer"
+]

changedOutput schema / properties / profiles / items / properties / profile / enum

Previous value: -[
-  "pr_test_analyzer",
-  "code_reviewer",
-  "security_reviewer",
-  "silent_failure_hunter",
-  "code_explorer",
-  "typescript_reviewer",
-  "react_reviewer",
-  "ruby_reviewer",
-  "python_reviewer",
-  "mobile_reviewer",
-  "omission_auditor"
-]New value: +[
+  "pr_test_analyzer",
+  "code_reviewer",
+  "security_reviewer",
+  "silent_failure_hunter",
+  "code_explorer",
+  "typescript_reviewer",
+  "react_reviewer",
+  "ruby_reviewer",
+  "python_reviewer",
+  "mobile_reviewer"
+]

Changed3 schema fields changedv0.2.16Oct 20, 2026

changedOutput schema / properties / bundles / items / properties / execution_groups / items / items / enum

Previous value: -[
-  "pr_test_analyzer",
-  "code_reviewer",
-  "security_reviewer",
-  "silent_failure_hunter",
-  "code_explorer",
-  "typescript_reviewer",
-  "react_reviewer",
-  "ruby_reviewer",
-  "python_reviewer",
-  "mobile_reviewer"
-]New value: +[
+  "pr_test_analyzer",
+  "code_reviewer",
+  "security_reviewer",
+  "silent_failure_hunter",
+  "code_explorer",
+  "typescript_reviewer",
+  "react_reviewer",
+  "ruby_reviewer",
+  "python_reviewer",
+  "mobile_reviewer",
+  "omission_auditor"
+]

changedOutput schema / properties / bundles / items / properties / profiles / items / enum

Previous value: -[
-  "pr_test_analyzer",
-  "code_reviewer",
-  "security_reviewer",
-  "silent_failure_hunter",
-  "code_explorer",
-  "typescript_reviewer",
-  "react_reviewer",
-  "ruby_reviewer",
-  "python_reviewer",
-  "mobile_reviewer"
-]New value: +[
+  "pr_test_analyzer",
+  "code_reviewer",
+  "security_reviewer",
+  "silent_failure_hunter",
+  "code_explorer",
+  "typescript_reviewer",
+  "react_reviewer",
+  "ruby_reviewer",
+  "python_reviewer",
+  "mobile_reviewer",
+  "omission_auditor"
+]

changedOutput schema / properties / profiles / items / properties / profile / enum

Previous value: -[
-  "pr_test_analyzer",
-  "code_reviewer",
-  "security_reviewer",
-  "silent_failure_hunter",
-  "code_explorer",
-  "typescript_reviewer",
-  "react_reviewer",
-  "ruby_reviewer",
-  "python_reviewer",
-  "mobile_reviewer"
-]New value: +[
+  "pr_test_analyzer",
+  "code_reviewer",
+  "security_reviewer",
+  "silent_failure_hunter",
+  "code_explorer",
+  "typescript_reviewer",
+  "react_reviewer",
+  "ruby_reviewer",
+  "python_reviewer",
+  "mobile_reviewer",
+  "omission_auditor"
+]

Changed2 schema fields changedv0.2.5Oct 12, 2026

addedOutput schema / properties / bundles / items / properties / execution_groups

Added value: +{
+  "description": "Ordered execution waves. Profiles in the same group are independent and may be reviewed concurrently; finish each group before starting the next.",
+  "items": {
+    "items": {
+      "enum": [
+        "pr_test_analyzer",
+        "code_reviewer",
+        "security_reviewer",
+        "silent_failure_hunter",
+        "code_explorer",
+        "typescript_reviewer",
+        "react_reviewer",
+        "ruby_reviewer",
+        "python_reviewer",
+        "mobile_reviewer"
+      ],
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "type": "array"
+}

changedOutput schema / properties / bundles / items / required

Previous value: -[
-  "bundle",
-  "when_to_use",
-  "profiles"
-]New value: +[
+  "bundle",
+  "when_to_use",
+  "profiles",
+  "execution_groups"
+]

Addedv0.1.24Sep 30, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety is covered. The description adds genuinely non-obvious context: the catalog is static, requires no session or arguments, and is unaffected by active sessions or configured models. It stops short of describing the response shape, but an output schema exists to carry that.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose in the first sentence, then routes. The bulleted alternative map is dense but each entry carries routing value; it is slightly longer than strictly necessary for a zero-argument catalog read.

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

Completeness5/5

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

With an output schema present, return values need no explanation, and the description covers everything else an agent needs: what the catalog contains, when to consult it, that it is static and argument-free, and which sibling handles each follow-up action.

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?

Zero parameters, so the baseline is 4. The description reinforces this by noting 'no session or arguments required,' which prevents an agent from inventing a session_id or filter argument.

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?

States a specific verb and resource ('Read the static profile/bundle catalog') and enumerates its contents (specialists, review scopes, execution schedules), which no sibling covers. An agent can distinguish it from prepare_qa_orchestration, start_qa_orchestration, and list_qa_orchestrations without opening any schema.

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

Usage Guidelines5/5

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

Explicitly states when to use it ('before creating a session or choosing its triage route') and routes to alternatives by scenario: standalone/recovery lookup goes to prepare_qa_orchestration(_bundle), session creation to start_qa_orchestration, route setting to advance_qa_orchestration, session listing to list_qa_orchestrations. It also clarifies that task-type recommendations are shortlists, not restrictions.

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

Deploy Server