TheySaid

Get test status

get_test_status

Read-onlyIdempotent

Returns a one-off progress snapshot for a running usability test: phase, an approximate percent complete and, for a failed run, failureReason ("partial" means the run was limited). Runs normally take several minutes. wait_for_results is the usual way to follow a test to completion.

Input Schema

Name	Required	Description	Default
`testId`	Yes

Output Schema

Name	Required	Description
`phase`	No
`updatedAt`	No
`etaSeconds`	No
`perPersona`	No
`projectUrl`	No	The test's project in the TheySaid app — share it when the user asks where the test is.
`failureReason`	No
`findingsSoFar`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 16, 2026

addedOutput schema / 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.1/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: typical run duration ('several minutes') and the meaning of 'partial' and failureReason, which an agent needs to interpret a snapshot.

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?

Two tight sentences with the core purpose front-loaded and the alternative named last. The field enumeration in the first sentence is dense but every clause carries information.

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?

With an output schema present, the description needn't explain return values, yet it usefully summarizes them and adds timing plus an alternative tool. Nothing an agent needs to invoke it correctly is missing, though testId provenance is unstated.

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 coverage is 0% and the single testId parameter has no description in either schema or description. The phrase 'for a running usability test' loosely implies testId identifies the test, but no format or source is given. Acceptable given the trivial single-param surface, but not enriched.

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 names a specific verb+resource ('one-off progress snapshot for a running usability test') and enumerates the returned fields (phase, percent complete, failureReason). It clearly differentiates this lightweight snapshot from the sibling that follows a test to completion.

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 explicitly routes the agent: 'wait_for_results is the usual way to follow a test to completion,' implying this tool is for quick point-in-time checks. It does not mention get_test_results, but the when-to-use-vs-alternative signal is clear.

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?