Skip to main content
Glama

AlgoRover Research

list_backtest_trades

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": "list_backtest_trades"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo
localeNoen
backtest_idYes

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo
schema_versionNo2.0

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 two useful behavioral facts beyond that – results are paginated and scoped to the caller's own backtests – but says nothing about what is returned for a non-completed or empty backtest.

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; the scope qualifier comes before the action. It is efficient, though its brevity borders on under-specification rather than tight writing.

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?

Rich annotations plus an output schema mean return values need no explanation, but with 4 undocumented parameters and no statement of preconditions or empty-result behavior, the definition leaves real gaps for a paginated retrieval 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% across 4 parameters, so the description carries the burden and only partially does: '分页' hints at limit/cursor but never explains cursor tokens, the limit ceiling of 100, or the locale enum. An agent must infer parameter meaning entirely from schema titles.

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?

States a specific verb and resource (分页读取…成交明细 – paginated read of trade details) plus a scope constraint (本人已完成回测 – the caller's own completed backtest). That scope distinguishes it from result/report siblings, though no sibling is named explicitly.

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?

'已完成' (completed) implicitly tells the agent the backtest must have finished before this tool applies, and '分页' implies repeated paging. There is no explicit when-to-use vs. alternatives (e.g., get_backtest_result) and no guidance on what to do while a backtest is still running.

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.