Skip to main content
Glama

AlgoRover Research

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

Input Schema

NameRequiredDescriptionDefault
localeNoen
backtest_idYes

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo
schema_versionNo2.0

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that the response includes the error state and the retention period, which implies jobs expire and disappears after some time; that is real context beyond the annotations. It still does not say whether polling is intended or how long retention lasts.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no waste, and the key content (status, errors, retention) is front-loaded. However, the brevity borders on under-specification for a tool with sibling overlap and undocumented parameters, so it is efficient without being complete.

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 do not need explanation, and the annotations cover safety. That leaves the description adequate on behavior but silent on parameter meaning and on the distinction from result and download tools. For a polling-style status tool, a mention of the relationship to get_backtest_result would close the remaining gap.

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 neither backtest_id's expected format (though a regex exists) nor locale's effect on the response is explained anywhere. The description only implies that backtest_id refers to the caller's own job, without covering locale at all. With two undocumented parameters, the description under-compensates for 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 names a specific verb and resource: it queries the status, errors, and retention period of a backtest job, and it scopes the results to the caller's own jobs. This is far clearer than a bare title, but it never distinguishes the tool from near neighbors such as get_backtest_result or get_backtest_report_download. The implicit split between 'status' and 'result' is helpful but not stated.

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

Usage Guidelines2/5

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

The description gives no explicit guidance on when to use this tool instead of get_backtest_result, get_backtest_report_download, or list_backtests, and it does not say whether it should be polled. Apart from the vague 'own' scope, an agent must infer the usage conditions from sibling names alone.

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.