Skip to main content
Glama

Restore a deleted strategy

acubic_restore_strategy
Idempotent

Restores a strategy deleted with acubic_delete_strategy, with its holdings, settings and backtest, within 30 days. acubic_list_strategies with mode archived lists the ones that can be restored.

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_restore_strategy"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoThe language of this conversation.
strategy_idYesA deleted strategy (acubic_list_strategies mode archived).

Output Schema

NameRequiredDescriptionDefault
errorNo
restoredNo
strategyNo
already_activeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false; the description adds the substantive context an agent actually needs — that the restore is time-bounded (30 days) and that it reinstates dependent state (holdings, settings, backtest) rather than an empty shell. It does not describe failure behavior past the 30-day window or name-collision handling, which keeps it below a 5.

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

Conciseness5/5

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

Two sentences, no filler. The core action and its time window come first, and the discovery hint comes second where it belongs.

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

Completeness4/5

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

For a single-required-parameter mutation with an output schema and full annotation coverage, the description supplies what the structured fields cannot: the 30-day window and the exact set of restored entities. Only edge cases — what happens on expiry or conflict — are left unstated, which is acceptable given the low complexity.

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

Parameters3/5

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

Schema coverage is 100%, including the note that strategy_id is a deleted strategy discoverable via list_strategies mode archived, so the description is largely restating structured data. The 'within 30 days' constraint implicitly narrows which IDs are valid, which is marginal added meaning over the schema.

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?

Specific verb+resource ('Restores a strategy') plus scope of what comes back ('holdings, settings and backtest') and a hard limit ('within 30 days'). It also anchors the tool to the sibling that created the deleted state ('deleted with acubic_delete_strategy'), so an agent can distinguish restore from create/get without opening schemas.

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

Usage Guidelines4/5

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

It states the precondition for use (the strategy must have been deleted within 30 days) and routes the agent to acubic_list_strategies with mode archived to discover eligible IDs. It does not explicitly say when not to use it (e.g., for a live strategy, where acubic_update_strategy or acubic_get_strategy would be correct), but the guidance is clear enough to act on.

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