Nopaque TotalPath

List Digital Test Configs

listDigitalTestConfigs

Read-onlyIdempotent

List the saved digital (chat) test configs in your workspace, newest first: each has an id, name, description, kind (freeform, compliance or standard), sector, mission, acceptance, the bot it talks to (targetRef, and connectorId or an inline target), and its steps or probes. Takes optional limit (1 to 200, default 50) and cursor (nextCursor from the previous page; absent on the last page). Use when: the user names a chat or bot test and you need its id, or asks what digital tests exist. These are NOT voice tests: for those use listTestConfigs or listMissionTestConfigs. Cross-tool: for the runs of a bot use listDigitalTestRuns with its targetRef. Read-only. Needs a role or key with digital:read. Configs are workspace-scoped.

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": "listDigitalTestConfigs"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Rejected with 400 outside 1-200 rather than silently clamped.
`cursor`	No	Opaque base64 cursor from `nextCursor` in a previous response.

Output Schema

Name	Required	Description	Default
`configs`	Yes
`nextCursor`	No	Opaque base64 cursor. Present ONLY when another page exists, and OMITTED (not null) on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, non-open-world, so the safety profile is covered. The description still adds real context beyond them: newest-first ordering, the authorization requirement (digital:read role or key), and workspace scoping. It stops short of describing result volume or default page size limits on the whole collection, but the important operational facts are present.

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?

The core purpose and field list are front-loaded, and the usage, exclusion, and cross-tool sentences are short and scannable. A few clauses duplicate what the input schema already documents (limit default, cursor origin), which is minor waste but otherwise every sentence does work.

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 values need not be explained, and the description still covers purpose, triggering conditions, sibling exclusions, cross-tool follow-ups, auth, scoping, and pagination termination. Nothing an agent needs in order to call this 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 pagination semantics the schema does not state: cursor comes from the previous page's nextCursor and is absent on the last page, which tells the agent how to detect the end of iteration. The limit range and default are restated from the schema rather than extended, so it is not a 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 and resource plus scope and ordering ("List the saved digital (chat) test configs in your workspace, newest first") and enumerates the returned fields. It explicitly separates itself from the voice-test siblings listTestConfigs and listMissionTestConfigs, so an agent can route without opening a 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" clause with two concrete triggers (need a chat/bot test's id, or asking what digital tests exist), an explicit exclusion ("These are NOT voice tests") naming the alternatives to use instead, and a cross-tool pointer to listDigitalTestRuns keyed on targetRef.

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.