Skip to main content
Glama

AlgoRover Research

get_backtest_report_download

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_report_download"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoen
backtest_idYes
artifact_kindNoreport_bundle

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo
schema_versionNo2.0

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds two traits not present in the annotations: the returned URL is short-lived ('短期'), which implies expiry and possible re-fetch, and access is scoped to the caller's own reports. It omits the expiry duration and the failure mode when the report is absent.

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, and the key constraint (own existing report, short-term link) comes first. It is, however, arguably undersized for the amount of undocumented schema surface it must carry.

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 with three parameters at 0% schema coverage and an enum offering five distinct artifact kinds, the description leaves the agent without the information needed to pick artifact_kind or understand the locale option, which is a material gap for this tool.

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% and the description mentions no parameter at all. With five enum values for artifact_kind (report_bundle, metrics_json, trades_csv, equity_png, configuration_json) and an undocumented locale parameter, the description does nothing to help an agent choose which artifact to download or explain the locale's effect.

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 states a specific verb and resource: generating a short-lived download address ('生成短期下载地址') for a report file ('报告文件'). Scope is also narrowed to the caller's own already-existing reports ('本人已存在'), so an agent can distinguish this from retrieval tools like get_backtest_result or get_backtest. It stops short of naming any sibling to contrast with.

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?

Usage is only implied: '已存在的' signals the precondition that the backtest report must already exist, and '本人' restricts it to the caller's own artifacts. There is no explicit statement of when to prefer this over get_strategy_download or the other report/result readers, and no guidance on what happens if no report exists.

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.