Nopaque TotalPath

List Digital Test Runs

listDigitalTestRuns

Read-onlyIdempotent

List digital (chat) test runs in your workspace, newest first: each has an id, targetRef (the bot), kind, sector, status (pending, running, completed, failed, cancelled), outcome, how many samples were requested and judged, passed, failed and transportErrors (chats that never got a verdict), passRate, failureReason, startedAt and completedAt. Takes optional targetRef (exact, e.g. acme/billing-bot: only that bot's runs), limit (1 to 200, default 50) and cursor (nextCursor from the previous page; absent on the last page). Use when: the user asks how a chat bot's tests went, or for the latest digital runs. outcome and transportErrors are separate on purpose: a bot that answers well but drops chats has a delivery problem, not a behaviour one. For one run's transcript and judge reasoning use getDigitalTestRun. Voice runs are in listTestRuns, not here. Read-only. Needs digital:read.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "listDigitalTestRuns"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Rejected with 400 outside 1-200 rather than silently clamped.
`cursor`	No	Opaque base64 pagination cursor from `nextCursor` in a previous response.
`targetRef`	No	Restrict to one target (the chat analogue of a phone number).

Output Schema

Name	Required	Description	Default
`runs`	Yes
`nextCursor`	No	Opaque base64 cursor. Present ONLY when another page exists, and OMITTED (not null) on the last page, so a generated `while (res.nextCursor)` paginator terminates.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint, yet the description still adds real context beyond them: required scope 'digital:read', newest-first ordering, cursor behavior ('absent on the last page'), and the design note that outcome and transportErrors are deliberately separate. The only deduction is that 'Read-only.' merely restates the annotation.

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

Conciseness3/5

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

The ordering is sound (purpose, payload, parameters, usage, differentiation), but a full field-by-field enumeration of the response (id, targetRef, kind, sector, status, outcome, counts, passRate, failureReason, startedAt, completedAt) duplicates the existing output schema. Trimming that list to the two fields that carry semantic nuance would tighten the definition considerably.

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?

Has an output schema and full annotation coverage, and the description still supplies the auth scope, ordering, pagination termination rule, and the semantic distinction between outcome and transportErrors. Nothing an agent needs in order to call it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds format meaning the schema lacks: targetRef is an exact match with a concrete example ('acme/billing-bot'), and cursor is tied to the previous response's nextCursor. It largely echoes the limit range (1-200, default 50) already in the schema, which caps it below 5.

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?

Opens with a specific verb+resource+scope ('List digital (chat) test runs in your workspace, newest first') and explicitly distinguishes itself from both getDigitalTestRun (single run transcript) and listTestRuns (voice). An agent can route correctly 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?

Provides an explicit 'Use when:' trigger ('the user asks how a chat bot's tests went, or for the latest digital runs') and names the two alternatives with the conditions that select them: getDigitalTestRun for transcripts, listTestRuns for voice. Exclusions are stated, not implied.

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

All Nopaque TotalPath 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.