Skip to main content
Glama
Sign In

Stride — AI software delivery platform

by page.stride
OverviewDiscussionsAdmin

Create retest run from failed tests

stride.rerun_failed_tests

Create a child test run seeded with the failed + blocked cases of a parent run (parentRunId links the chain). Inherits the parent suite + environment; each eligible case is seeded BLOCKED. Soft-errors when the parent had no failing or blocked cases. Returns the new run id + retried count.

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": {
      "testRunId": "<testRunId>"
    },
    "name": "stride.rerun_failed_tests"
  }
}

Input Schema

NameRequiredDescriptionDefault
testRunIdYesUUID of the parent test run.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Adds substantial context beyond annotations: inheritance of suite and environment, that each eligible case is seeded BLOCKED, the soft-error fallback, and the return shape. Annotations already cover safety (destructiveHint false), but the description doesn't address repeat invocations — with idempotentHint=false, an agent could benefit from knowing each call appends a new run to the chain.

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?

Three dense sentences, front-loaded with the action and seed criterion, then inheritance facts, then error/return behavior. No filler and nothing repeated from the schema.

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 single-parameter creation tool with no output schema, the description covers inputs, side effects, error behavior, and return values — everything needed to call it correctly. No material gaps remain.

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% for the single parameter, so baseline is 3. The description still adds value by framing testRunId as the parent whose failure set is copied and as the link in the retest chain, which the terse schema text ('UUID of the parent test run') only partially conveys.

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 ('Create a child test run') plus the exact seeding rule (failed + blocked cases of a parent run), which cleanly distinguishes it from the sibling create_test_run. An agent can tell what this produces without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The retest-after-failure scenario is clearly implied by 'seeded with the failed + blocked cases of a parent run', and the soft-error condition (parent has no failing/blocked cases) tells the agent when the call is pointless. It does not explicitly name create_test_run as the non-retest alternative, so it falls short of full when/when-not routing.

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

All Stride — AI software delivery platform toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources