Skip to main content
Glama

AlgoRover Research

prepare_backtest

Read-onlyIdempotent

准备固定版本、预设和历史窗口,返回预览;不创建回测。

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": {
      "strategy_ref": "<strategy_ref>",
      "preset": "<preset>",
      "venue": "<venue>",
      "days": "<days>"
    },
    "name": "prepare_backtest"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYes
venueYes
localeNoen
presetYes
strategy_refYes

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo
schema_versionNo2.0

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered by structured data. The description adds only the preview/read-only framing, which largely restates the annotations, and says nothing about what validation failures look like, whether the preview expires, or what the agent should do with it. Credit for consistency, but little added behavioral depth.

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?

A single tight sentence with the positive capability front-loaded and the exclusion after the semicolon; nothing is wasted. However, one clause is thin for a 5-parameter tool with an undescribed nested object, so it reads as terse rather than optimally sized.

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

Completeness2/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 explained, but the input side is largely unaddressed: five parameters, four required, a nested StrategyRef with a strict sha256 pattern, two enums and two pattern-constrained strings are all left to the schema. For a preparation/preflight tool whose whole value is telling the agent what will be validated and pinned, this leaves significant gaps.

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% across 5 parameters, so the description carries the full burden and mostly fails it. It maps loosely to strategy_ref (pinned version), preset and days (historical window), but adds no meaning for venue, locale, or the package_sha256 field inside StrategyRef, and never explains why days is restricted to 90 or 365.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete verb and the three things it resolves (pinned version, preset, historical window) and states that it returns a preview, so an agent knows this is a resolution/preflight step rather than an execution step. It falls short of 5 because it never names the sibling it hands off to (start_backtest), relying on the negative clause alone for differentiation.

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

Usage Guidelines3/5

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

"Does not create a backtest" implies this belongs before start_backtest, which is useful routing context, but the guidance is implied rather than stated. There is no explicit when-to-use or when-not-to-use beyond that negation, and no mention of prerequisites such as whether a prior prepare_strategy call is required.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.