Skip to main content
Glama

AlgoRover Research

get_backtest_result

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": {
      "backtest_id": "<backtest_id>"
    },
    "name": "get_backtest_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoen
backtest_idYes
equity_max_pointsNo

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 readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds useful context that the returned curve is 有限 (limited/truncated) and that 复现 (reproduction) data is included, which signals the response is a bounded snapshot rather than the raw series. It does not say what happens when the backtest is incomplete or whether metrics are final.

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 front-loaded sentence with no filler; every clause conveys a distinct part of the payload. It is efficient, though its terseness is part of why parameter and error semantics go undocumented.

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 described, and annotations cover the safety profile. The remaining burden is the three undocumented parameters and the failure mode for incomplete or unauthorized backtests, neither of which is addressed for a tool that is otherwise simple to call.

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 burden for all three parameters, yet it explains none of them explicitly. The phrase 有限曲线 hints at the equity_max_points cap and 本人 hints at ownership scoping via backtest_id, but locale, the id pattern, and the 2–1024 point range are left entirely to the schema without added meaning.

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 (读取/read) with a specific resource: the metrics, equity curve, and reproduction information of one's own completed backtest. The qualifier 已完成 (completed) narrows scope meaningfully versus get_backtest or list_backtests. It does not name a sibling to distinguish from get_backtest_report_download, so it stops short of a 5.

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?

Use is implied by the precondition that the backtest must be 已完成 (completed), which tells an agent not to call it on running or failed runs. However, there is no explicit statement of when to prefer this over get_backtest, get_backtest_report_download, or list_backtest_trades, and no stated behavior for requesting a non-completed run.

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.