Nopaque TotalPath

Get Sweep Run

getSweepRun

Read-onlyIdempotent

Get one sweep run by id, with its status and summary worked out from its test runs, and testRuns: one row per persona with the test run id, testConfigId, profileId, status, outcome and times. Use when: the user asks which personas passed or failed in a sweep. For why one persona's run failed use getRunResults with its test run id. Read-only for the caller. Needs testing:read. Returns 404 if the run 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": "getSweepRun"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Sweep run identifier.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond annotations it discloses the required scope (testing:read), the 404 workspace-scoping behavior, and the non-obvious fact that status/summary are computed from constituent test runs rather than stored. The 'Read-only for the caller' line restates readOnlyHint but is harmless.

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-loaded with purpose, then usage, then constraints — no filler sentences. The inline enumeration of `testRuns` fields is somewhat redundant given an output schema exists, but it is compact and readable.

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 with full annotations and an output schema, everything an agent needs is present: trigger condition, alternative routing, auth scope, and error behavior. Nothing forces the agent to guess.

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 there is only one parameter, so little is required. The description still adds value by distinguishing the sweep run `id` from the test run id used by getRunResults, which is the main misuse risk for a single-uuid lookup.

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 ('Get one sweep run by `id`') and immediately enumerates what the response contains (derived status/summary plus a per-persona `testRuns` row). This distinguishes it cleanly from sibling lookups like getSweep and getRunResults.

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 trigger ('Use when: the user asks which personas passed or failed in a sweep') and routes the adjacent case elsewhere ('For why one persona's run failed use getRunResults with its test run id'). It even specifies which id flavor the alternative needs, removing a likely confusion.

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.