Nopaque TotalPath

List Runs of a Sweep

listSweepRuns

Read-onlyIdempotent

List the runs of one sweep, by the sweep's id: each run has an id, status, a summary (total, pending, running, passed, failed, error), the test run ids it started, when it started and finished, and whether it was started by hand or by a schedule. Use when: the user asks how a named sweep has been doing. For every sweep run in the workspace use listSweepRunsForWorkspace; for one run's per-persona results use getSweepRun. Read-only. Needs testing:read. Returns 404 if the sweep is not in your workspace.

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": {
      "id": "<id>"
    },
    "name": "listSweepRuns"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Sweep identifier.

Output Schema

Name	Required	Description	Default
`runs`	Yes

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 readOnlyHint, idempotentHint and destructiveHint=false, so the description does not need to re-argue safety, yet it still adds real context beyond them: it repeats read-only for emphasis, states the required testing:read scope, and discloses the 404 behavior when the sweep is outside the workspace. That permission and error contract are genuinely extra information not present in 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.

Conciseness4/5

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

Front-loads the action and scope, then routes to alternatives, then states rules; every sentence carries weight. The inventory of run fields (status, summary counts, test run ids, timestamps, manual vs schedule) is slightly verbose given an output schema exists, but it usefully signals what the agent can report.

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?

For a one-parameter read tool this covers scope, alternative routing, auth requirement, error case, and the shape of returned data. Nothing an agent needs in order to call it correctly or interpret it 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% and the single id parameter is documented as a UUID sweep identifier, so the baseline is 3; the description adds that the id belongs to the sweep (not a run) and that an out-of-workspace sweep yields 404, clarifying the parameter's failure semantics.

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 the runs of one sweep) scoped by the sweep id, and immediately distinguishes itself from listSweepRunsForWorkspace (all sweeps) and getSweepRun (per-persona results). An agent can pick this tool 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 when-to-use trigger ("the user asks how a named sweep has been doing") and names both alternatives with the conditions that select them: workspace-wide listing and single-run per-persona detail. Nothing is left to inference.

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.