Skip to main content
Glama

AlgoRover Research

delete_backtest_result

DestructiveIdempotent

删除本人终态回测结果并撤销文件访问。

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

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

B3.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is known; the description goes beyond them by disclosing a side effect they don't capture — that file access is revoked (撤销文件访问) and that deletion is scoped to the caller's own terminal results. It stops short of stating irreversibility or whether the files are purged or merely unlinked.

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 tight sentence with the action and both scope constraints front-loaded and no filler. It is arguably too terse for a destructive operation, but no wording is wasted.

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 needn't be explained, and the low-complexity two-parameter shape limits what is missing. Still, a destructive tool leaves the agent without parameter guidance and without a clear statement of what is destroyed versus made inaccessible.

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 two parameters, so the description should carry the load, and it does not mention backtest_id or locale at all. The identifier's meaning is inferable from the tool name, but the locale switch and its accepted values are documented nowhere.

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?

A concrete verb (删除) plus a precise resource (回测结果), narrowed by two scope qualifiers: 本人 (only the caller's own results) and 终态 (only terminal-state results). That distinguishes it from get_backtest_result and cancel_backtest without needing their schemas, though no sibling is named directly.

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 preconditions (own data, terminal state only) imply when the tool applies, but they are stated as constraints rather than as explicit routing guidance. Nothing tells the agent why to pick this over cancel_backtest or delete_research_data, or what to do when a result 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.