Skip to main content
Glama

AlgoRover Research

cancel_backtest

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": "cancel_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.8/5.0
Behavior3/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 covered. The description adds two pieces of context beyond that: '本人' restricts the operation to the caller's own backtests (an authorization scope), and '请求' (request) hints that cancellation may be a request rather than an immediate effect. It says nothing about what state the job ends in or what happens to already-produced results.

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?

One short sentence with zero waste and the object of the action front-loaded, which is good. However, the extreme brevity tips into under-specification rather than disciplined conciseness, so there is no structural payoff for the terseness.

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 this is a destructive, idempotent mutation with two undocumented parameters and no stated preconditions or postconditions; for that complexity level the description is far too thin to let an agent call it confidently.

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 must carry the burden of explaining backtest_id and locale, and it does not. It only obliquely implies that backtest_id must identify one of the caller's own backtests; the locale parameter and the ID format constraint are left entirely to the schema.

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 single clause names a specific verb (请求取消, request cancellation) and a specific resource (回测, backtest), and adds the scope '本人' (one's own). An agent can distinguish this from delete_backtest_result (which removes a result, not a job) without opening the schema. It stops short of an explicit sibling contrast, so it is clear but not fully differentiating.

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?

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites (e.g., the backtest must be running), and no reference to alternatives such as delete_backtest_result. The only implied constraint is that the target must belong to the caller.

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.