Back to MCP catalog
release_holdout

Permanently discard a project's reserved holdout window.

Area

Backtesting & Validation

Group

Holdout

Access

Write

Risk

Destructive

Details

Full description

Discard a project's reserved holdout window (escape hatch). Clears holdout_start, holdout_end and resets holdout_validation_count. Permanent — a holdout window is allocated once, at project creation, and nothing re-allocates one after release, so the project is left with no reserved holdout at all.

Use this to recover when a backtest range falls entirely inside a stale reserved holdout (the run_backtest error points here).

Destructive — this throws away out-of-sample-integrity state (prior holdout validations no longer correspond to the reserved window), so it requires confirm=true. With confirm=false it is a no-op that just reports the current holdout window.

Args

  • project_id — project whose holdout window to release.
  • confirm — must be true to actually release.
release_holdout(project_id, confirm=true)

Capabilities

Bounded options and operating modes surfaced above the full JSON schema.

No bounded capability options are declared for this tool.

Required Inputs

project_idstringResearch project identifier

Optional Inputs

confirmbooleanMust be true to actually release the holdout. This discards research-integrity state, so it is a no-op unless confirm=true.
Quawd

A subscription SaaS platform for designing, backtesting, and paper-trading algorithmic trading strategies on equities and crypto — described in plain English to an AI agent, no code required.

© 2026 Quawd. All rights reserved.

Quawd is a software tool, not a broker-dealer or investment adviser, and does not provide investment advice. Trading involves substantial risk of loss. Backtested and hypothetical results have inherent limitations and are not indicative of future performance.