Backtrader MCP

Overview Schema Source Related Servers Discussions Admin

Prepare Strategy Run

prepare_strategy_run

Idempotent

Freeze backtest inputs into a signed run plan that requires local approval. Specify dataset, draft, and optional parameter grid to generate a command for authorized execution.

Instructions

Freeze exact run inputs and return a signed plan requiring local approval.

    The response includes the printed local approval command. A separate
    execution approval is mandatory before start_strategy_run. For
    run_profile_id=parameter_sweep, param_grid maps StrategySpec parameter
    names to value lists (at most 64 combinations); one approval covers
    the whole grid.

Input Schema

TableJSON Schema

Name	Required	Default
`draft_id`	Yes
`dataset_id`	Yes
`param_grid`	No
`runtime_id`	No	default
`run_profile_id`	No	fixed_tests
`idempotency_key`	No
`timeout_seconds`	No
`validation_token`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 20, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Beyond annotations, the description discloses meaningful behavior: the output is a signed plan requiring local approval, the response includes the printed approval command, and a second approval is needed before execution. It also specifies the param_grid combination limit and that one approval covers the entire grid. No contradiction with annotations exists.

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 compact and front-loaded. The core purpose appears in the first sentence, and the second sentence delivers targeted edge-case behavior. There is no filler or redundant restatement of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The approval workflow and parameter_sweep behavior are well covered, and the presence of an output schema reduces the need to describe return values. However, with eight parameters and zero parameter descriptions in the schema, the tool is not fully self-sufficient for an agent: critical fields like validation_token and runtime_id are left to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden of explaining parameters. It only adds semantic value for run_profile_id and param_grid. Required parameters like draft_id, validation_token, and dataset_id, plus others like runtime_id and timeout_seconds, remain unexplained, leaving an agent to infer their meaning from names and types alone.

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?

The description states a specific verb and resource: 'Freeze exact run inputs and return a signed plan requiring local approval.' This clearly contrasts with sibling run execution tool start_strategy_run and communicates what makes this preparation step distinct.

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 description clearly establishes the tool as a prerequisite to start_strategy_run by stating that 'a separate execution approval is mandatory before start_strategy_run.' It also gives conditional usage guidance for the parameter_sweep profile. It does not explicitly name alternatives or when-not-to-use cases, but the workflow context is clear.

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