Skip to main content
Glama

Delete a strategy

acubic_delete_strategy
DestructiveIdempotent

Deletes a draft or paper-money strategy by archiving it together with its saved backtest; it can be restored within 30 days (acubic_restore_strategy). A strategy with a broker connection is removed on acubic.ai. The person is asked to confirm, or the result gives a confirm_token to pass back once they agree. To stop a running backtest use acubic_cancel_backtest.

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": {
      "strategy_id": "<strategy_id>"
    },
    "name": "acubic_delete_strategy"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoThe language of this conversation.
strategy_idYesThe draft or paper-money strategy to delete.
confirm_tokenNoFor clients without elicitation: the confirm_token from the first call's confirmation_required result, sent once the person agreed.

Output Schema

NameRequiredDescriptionDefault
nameNo
errorNo
deletedNoFalse when the confirmation was declined: nothing changed.
deleted_atNo
restore_urlNoSigned-in page that restores the strategy; valid for restorable_days.
strategy_idNo
archived_withNoWhat was archived along with the strategy and comes back with a restore.
restorable_daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare destructive=true and readOnly=false; the description adds the crucial detail that this is a soft delete via archiving, recoverable for 30 days, and that broker-connected strategies are removed a different way. It also discloses the required human confirmation step and the confirm_token round-trip, which the annotations do not convey at all.

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?

The core behavior is front-loaded and each sentence carries information. It is somewhat dense, with the confirmation-flow clause spliced together by "or" and several parenthetical sibling references, which mildly reduces scannability but nothing is genuinely wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive tool with an output schema and full annotation coverage, the description supplies exactly the missing pieces: recoverability window, the archive-vs-remove distinction, the two-step confirmation contract, and the correct alternative for cancelling a backtest. An agent has everything needed to invoke it safely and correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds procedural meaning the schema does not: that confirmation is expected and that on agreement the person's confirm_token is passed back on a second call. It adds nothing about the locale enum, which the schema already covers.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first clause names a specific verb and resource ("Deletes a draft or paper-money strategy") and immediately explains the mechanism (archiving together with its saved backtest). It explicitly differentiates from the sibling acubic_restore_strategy and from acubic_cancel_backtest, so an agent can pick the correct tool without opening any schema.

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

Usage Guidelines5/5

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

It names when to use this tool versus three concrete alternatives: restore within 30 days for reversal, acubic_cancel_backtest for a running backtest, and the implicit acubic.ai route for broker-connected strategies. Exclusions are stated, not inferred.

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.

Resources