TheySaid

Wait for results

wait_for_results

Read-onlyIdempotent

Waits server-side, for a bounded window, for a usability test to finish, and sends progress notifications meanwhile, so no polling is needed. Returns message (a user-facing summary), phase and, once finished, results (the same data as get_test_results, including resultsMarkdown). If the window elapses first, stillRunning is true; long runs are normal, and calling wait_for_results again continues waiting. For a "partial" or "failed" run, the partial findings and instant design scan are included. Optional maxWaitSeconds shortens a single wait.

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": {
      "testId": "<testId>"
    },
    "name": "wait_for_results"
  }
}

Input Schema

Name	Required	Description	Default
`testId`	Yes
`maxWaitSeconds`	No

Output Schema

Name	Required	Description
`phase`	No
`status`	No
`message`	No	User-facing framing the caller can relay verbatim.
`results`	No	Populated on a terminal phase; null while still running.
`stillRunning`	No	True on timeout/abort while non-terminal — call again.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 11, 2026
- removedInput schema / properties / maxWaitSeconds / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / maxWaitSeconds / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / status / properties / etaSeconds / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / status / properties / etaSeconds / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / status / properties / failureReason / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / status / properties / failureReason / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed2 schema fields changedOct 16, 2026

changedOutput schema / properties / results / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "message": {
-        "type": "string"
-      },
-      "partial": {
-        "type": "boolean"
-      },
-      "phase": {
-        "enum": [
-          "planning",
-          "running",
-          "summarizing",
-          "done",
-          "partial",
-          "failed"
-        ],
-        "type": "string"
-      },
-      "prioritizedIssues": {
-        "items": {
-          "additionalProperties": false,
-          "properties": {
-            "conversationLink": {
-              "type": "string"
-            },
-            "detail": {
-              "type": "string"
-            },
-            "fixPrompt": {
-              "type": "string"
-            },
-            "id": {
-              "type": "string"
-            },
-            "severity": {
-              "enum": [
-                "high",
-                "med",
-                "low"
-              ],
-              "type": "string"
-            },
-            "title": {
-              "type": "string"
-            }
-          },
-          "required": [
-            "id"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "quickScan": {
-        "anyOf": [
-          {
-            "additionalProperties": false,
-            "properties": {
-              "caption": {
-                "type": "string"
-              },
-              "findings": {
-                "items": {
-                  "additionalProperties": false,
-                  "properties": {
-                    "detail": {
-                      "type": "string"
-                    },
-                    "severity": {
-                      "enum": [
-                        "high",
-                        "med",
-                        "low"
-                      ],
-                      "type": "string"
-                    },
-                    "title": {
-                      "type": "string"
-                    }
-                  },
-                  "type": "object"
-                },
-                "type": "array"
-              }
-            },
-            "type": "object"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "resultsMarkdown": {
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "message": {
+        "type": "string"
+      },
+      "partial": {
+        "type": "boolean"
+      },
+      "phase": {
+        "enum": [
+          "planning",
+          "running",
+          "summarizing",
+          "done",
+          "partial",
+          "failed"
+        ],
+        "type": "string"
+      },
+      "prioritizedIssues": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "conversationLink": {
+              "type": "string"
+            },
+            "detail": {
+              "type": "string"
+            },
+            "fixPrompt": {
+              "type": "string"
+            },
+            "id": {
+              "type": "string"
+            },
+            "severity": {
+              "enum": [
+                "high",
+                "med",
+                "low"
+              ],
+              "type": "string"
+            },
+            "title": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "id"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "projectUrl": {
+        "description": "The test's project in the TheySaid app — share it when the user asks where the test is.",
+        "type": "string"
+      },
+      "quickScan": {
+        "anyOf": [
+          {
+            "additionalProperties": false,
+            "properties": {
+              "caption": {
+                "type": "string"
+              },
+              "findings": {
+                "items": {
+                  "additionalProperties": false,
+                  "properties": {
+                    "detail": {
+                      "type": "string"
+                    },
+                    "severity": {
+                      "enum": [
+                        "high",
+                        "med",
+                        "low"
+                      ],
+                      "type": "string"
+                    },
+                    "title": {
+                      "type": "string"
+                    }
+                  },
+                  "type": "object"
+                },
+                "type": "array"
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "resultsMarkdown": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / status / properties / projectUrl

Added value: +{
+  "description": "The test's project in the TheySaid app — share it when the user asks where the test is.",
+  "type": "string"
+}

First observedOct 16, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses the blocking window semantics, that progress notifications are emitted during the wait, the stillRunning flag on timeout, that repeated calls resume waiting, and the special handling for partial/failed runs. That is exactly the behavioral context the annotations cannot express.

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 purpose is front-loaded in the first clause, then return shape, then timeout behavior, then edge cases for partial/failed runs and the optional parameter. Every sentence adds a distinct fact with no restatement of the name or title.

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

Completeness4/5

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

For a blocking, notification-emitting tool this covers nearly everything an agent needs: what blocks, what comes back, what stillRunning means, and how to continue. An output schema exists, so the enumerated return fields are a bonus rather than a necessity, and only the testId parameter is left entirely to inference.

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 description coverage is 0%, so the description carries the burden, and it does define maxWaitSeconds as an optional way to shorten a single wait. However, testId is never described and the relationship between maxWaitSeconds and the overall wait window across repeated calls is only loosely implied.

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 opens with a specific verb and resource: server-side waiting for a usability test to finish within a bounded window, with progress notifications replacing polling. It also distinguishes itself from get_test_results by noting that results are 'the same data as get_test_results' but delivered after a wait, so an agent can tell the two apart without opening either schema.

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?

It states the core usage condition plainly ('no polling is needed') and explains the long-run case: if the window elapses, call wait_for_results again to continue waiting. The alternative path, using get_test_results when you do not want to block, is implied by the comparison but never spelled out as an explicit when-to-use-this-instead rule.

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

All TheySaid tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?