Skip to main content
Glama

AlgoRover Research

prepare_strategy

Idempotent

为指定的已发布策略版本安排预设解析,不启动回测。

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>"
    },
    "name": "prepare_strategy"
  }
}

Input Schema

NameRequiredDescriptionDefault
retryNo
localeNoen
strategy_refYes

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo
schema_versionNo2.0

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=true). The description adds real value with the negative constraint that no backtest is launched, which clarifies the side effect is limited to arranging the preset resolution. It omits any mention of required permissions, effects on prior prepared state, or how openWorld behavior (remote package resolution) surfaces, so it earns credit without being rich.

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?

A single sentence, front-loaded with the action and resource, with the distinguishing constraint ('does not start a backtest') placed at the end where it lands as a clarifier. No filler or restated title.

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?

An output schema exists, so return values need not be described, and annotations carry the safety profile. Still, for a non-read-only tool whose parameters are fully undocumented in the schema, the description leaves the meaning of the preparation step and the roles of retry/locale unexplained, which is a meaningful gap for correct invocation.

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 three parameters: retry (boolean, default false), locale (en/zh-CN enum), and a nested strategy_ref carrying slug, version, and package_sha256. The description never mentions retry or locale, and the schema is an $ref-heavy nested object with no per-field prose. The only semantic added is that the strategy version must be published, which partly constrains strategy_ref but compensates for very little of the coverage gap.

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 pairs a specific verb (安排预设解析, 'arrange the preset resolution') with a specific resource (指定的已发布策略版本, 'the specified published strategy version') and explicitly negatives backtest start-up, which separates it from prepare_backtest/start_backtest. It stops short of 5 because '预设解析' is unexplained jargon, so an agent cannot fully picture the resulting artifact.

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?

The clause '不启动回测' implicitly routes the agent away from start_backtest and toward the preparation step, and '已发布' implies a publication precondition. However, there is no explicit statement of when this tool should be chosen over prepare_backtest or get_strategy, and no stated prerequisites beyond published-ness.

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.