QA Orchestrator

Overview Schema Source Related Servers Discussions Admin

List retained QA sessions

list_qa_orchestrations

Read-onlyIdempotent

Lists retained QA sessions and metadata so you can recover a lost run ID by matching task type, route, and stage, then confirm ambiguous matches.

Instructions

List non-expired QA session identifiers and brief metadata, including bound review identity.

Recover a lost run_id by matching task type, route, and stage; confirm if several match. Call get_qa_orchestration(run_id) for full state and next action, or get_qa_orchestration_model_policy() for server policy. Takes no arguments.

Includes retained terminal sessions; expired or evicted sessions are unrecoverable.
Sorts by expires_at descending, then run_id descending; empty means none are retained.
After restart, unfinished sessions and finalized sessions with saved review artifacts restored from configured local storage appear.
Reading does not extend session TTL.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`sessions`	Yes
`read_only`	No
`host_owns_decisions`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.2.20Oct 29, 2026

changedOutput schema / properties / sessions / items / properties / current_profile / anyOf

Previous value: -[
-  {
-    "enum": [
-      "pr_test_analyzer",
-      "code_reviewer",
-      "security_reviewer",
-      "silent_failure_hunter",
-      "code_explorer",
-      "typescript_reviewer",
-      "react_reviewer",
-      "ruby_reviewer",
-      "python_reviewer",
-      "mobile_reviewer",
-      "omission_auditor"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "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": "null"
+  }
+]

changedOutput schema / properties / sessions / items / properties / selected_profile / anyOf

Previous value: -[
-  {
-    "enum": [
-      "pr_test_analyzer",
-      "code_reviewer",
-      "security_reviewer",
-      "silent_failure_hunter",
-      "code_explorer",
-      "typescript_reviewer",
-      "react_reviewer",
-      "ruby_reviewer",
-      "python_reviewer",
-      "mobile_reviewer",
-      "omission_auditor"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "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": "null"
+  }
+]

Changed2 schema fields changedv0.2.16Oct 20, 2026

changedOutput schema / properties / sessions / items / properties / current_profile / anyOf

Previous value: -[
-  {
-    "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": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "pr_test_analyzer",
+      "code_reviewer",
+      "security_reviewer",
+      "silent_failure_hunter",
+      "code_explorer",
+      "typescript_reviewer",
+      "react_reviewer",
+      "ruby_reviewer",
+      "python_reviewer",
+      "mobile_reviewer",
+      "omission_auditor"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / sessions / items / properties / selected_profile / anyOf

Previous value: -[
-  {
-    "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": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "pr_test_analyzer",
+      "code_reviewer",
+      "security_reviewer",
+      "silent_failure_hunter",
+      "code_explorer",
+      "typescript_reviewer",
+      "react_reviewer",
+      "ruby_reviewer",
+      "python_reviewer",
+      "mobile_reviewer",
+      "omission_auditor"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

Changed5 schema fields changedv0.2.9Oct 13, 2026

changedOutput schema / properties / sessions / items / description

Previous value: -"Content-free metadata for identifying a retained session."New value: +"Bounded metadata for finding a retained orchestration session."

addedOutput schema / properties / sessions / items / properties / has_review_artifacts
```
Added value: +{
+  "default": false,
+  "type": "boolean"
+}
```

addedOutput schema / properties / sessions / items / properties / review_diff_sha256

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedOutput schema / properties / sessions / items / properties / review_head_sha

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedOutput schema / properties / sessions / items / properties / review_repository

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

Addedv0.1.23Sep 30, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations only cover the safety profile (readOnly, idempotent, closed-world). The description adds genuinely non-obvious traits: retention scope (terminal sessions retained, expired/evicted unrecoverable), deterministic sort order, restart/storage restoration behavior, and the fact that reading does not extend TTL. This is exactly the behavioral context an agent cannot get from structured fields.

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?

Front-loaded with the primary purpose in sentence one, followed by usage and alternatives, then three tight bullets for retention, ordering, and restart semantics. No sentence is redundant and each bullet carries distinct operational value.

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?

An output schema exists, so return-shape explanation is unnecessary. Between purpose, routing to alternatives, retention/expiry rules, sort order, and TTL behavior, the description covers everything an agent needs to decide to call this and interpret the results.

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?

The tool takes zero parameters, so per the rubric the baseline is 4. The description correctly notes 'Takes no arguments,' which is fully adequate; there is nothing further to specify.

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 ('List non-expired QA session identifiers and brief metadata') and immediately scopes it against the sibling that returns detail ('Call get_qa_orchestration(run_id) for full state'). An agent can distinguish this list tool from get_qa_orchestration and get_qa_orchestration_model_policy 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?

Gives an explicit use case ('Recover a lost run_id by matching task type, route, and stage; confirm if several match') and routes to two named alternatives for different needs (full state, server policy). It also states the calling constraint ('Takes no arguments'), leaving nothing to inference.

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

Deploy Server