Nopaque TotalPath

Get Mission Test Run

getMissionTestRun

Read-onlyIdempotent

Use when you have a mission-test run id and want the full AI-judged result: verdict (pass/fail/inconclusive/error), passReasoning, passEvidence, transcript, and compliance fields. Returns 404 for non-mission runs (compliance, standard, param) — use getRunResults for those. For listing across runs use listTestRuns; for counts and percentages use aggregateTestRuns. Returns 404 cross-workspace (D-02 strict type-gate).

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

Input Schema

Name	Required	Description	Default
`id`	Yes	Mission test run UUID.

Output Schema

Name	Required	Description
`id`	Yes
`passed`	No	AI judgement verdict for freeform mission runs.
`sector`	No
`status`	Yes
`audioId`	No
`carrier`	No	Bring-your-own-carrier (invite-only): the carrier route this run was dialled through, recorded when the run was dispatched. It still names that route after the config's `carrierRouteId` is changed or removed. Absent when the run was dialled normally. See `GET /testing/carrier-integrations` for the route's name and settings.
`mission`	No
`outcome`	No	Unified outcome. INCONCLUSIVE added in D-06 (revised).
`verdict`	No	Compliance verdict (compliance runs only).
`configId`	No	Set when launched from a saved MissionTestConfig (Phase 60.1).
`language`	No	The call language the run was dispatched with. Absent means English (every run before the field existed, and every run that did not set it).
`startedAt`	Yes
`acceptance`	No
`transcript`	No	Call transcript (string or structured).
`completedAt`	No
`phoneNumber`	No
`workspaceId`	Yes
`callPlacedAt`	No	The moment the dial returned a call_control_id (before the answered event) — distinct from `startedAt`, which is the api-side enqueue moment. Absent on rows cancelled before dial and on every pre-existing row.
`errorMessage`	No
`passEvidence`	No	Freeform mission evidence (string) or compliance evidence array.
`callControlId`	No
`passReasoning`	No
`advancedParams`	No	The turn-taking settings the run was dispatched with. Absent when none were set (server defaults applied) and on runs before 2026-11-05.
`judgeReasoning`	No
`complianceFailEvidence`	No
`compliancePassEvidence`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already establish readOnly, idempotent, non-destructive, and closed-world behavior, but the description adds substantive error semantics the annotations cannot convey: 404 for non-mission run types (compliance, standard, param) with a redirect, and 404 for cross-workspace access. The 'D-02 strict type-gate' label is internal jargon, but its observable effect (cross-workspace returns 404) is stated plainly.

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

Conciseness5/5

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

The description is front-loaded with the use condition, then the return payload, then the negative cases and alternatives. Every clause carries routing or behavioral information; there is no filler or repetition of the tool name.

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 specified, yet the description still names the key fields an agent will receive. Combined with the 404 and cross-workspace constraints, this is complete for a single-parameter read tool.

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?

There is a single required parameter and schema description coverage is 100%, with the schema already describing 'id' as a mission test run UUID. The description reinforces that the input must be a mission-test run id and excludes other run types, but adds no format or syntax detail beyond the schema, so the baseline of 3 applies.

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 ('getMissionTestRun' for a mission-test run id) and enumerates exactly what the full AI-judged result contains: verdict, passReasoning, passEvidence, transcript, and compliance fields. It also names the sibling tools it is not (getRunResults, listTestRuns, aggregateTestRuns), so an agent can separate it from neighbors without opening schemas.

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 condition ('when you have a mission-test run id and want the full AI-judged result') plus explicit exclusions and routing: non-mission runs go to getRunResults, cross-run listing to listTestRuns, counts/percentages to aggregateTestRuns. Both the positive case and the alternatives are covered, leaving little 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.