Skip to main content
Glama

Update a strategy

acubic_update_strategy
DestructiveIdempotent

Updates the name, description, filter rules, include lists or Exclude list of one saved strategy, and lists each previous value. Holdings are not recomputed. It cannot change the ranking, weighting, limits or sizes: for that build a new strategy with acubic_create_strategy. A strategy with a broker connection accepts name and description only.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
localeNoThe language of this conversation.
includeNoIds per acubic_list_strategy_options section (index: indices).
descriptionNonull clears it.
strategy_idYesThe strategy to change.
filter_rulesNo
response_formatNoconcise
excluded_symbolsNoThe whole Exclude list (replaces the saved one; [] clears it; up to 200 tickers, none locked). Never bought; a held one is sold at the next rebalance.

Output Schema

NameRequiredDescriptionDefault
errorNo
changesNo
strategyNo
strategy_idNoSet only with detail_unavailable.
passing_afterNoNames in the saved candidate pool that pass the new rules.
detail_unavailableNoTrue when the strategy could not be read after the change was saved; the change is saved.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered; the description adds genuinely non-obvious behavior such as holdings not being recomputed, previous values being listed, and the reduced field set for broker-connected strategies. It does not discuss whether a running backtest or live state blocks the update, which is the main remaining behavioral gap for a mutation tool.

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?

Three short sentences, front-loaded with the mutable surface, then constraints, then the alternative. The clause 'and lists each previous value' is slightly awkwardly appended to the first sentence and the mixed capitalization of 'Exclude list' is a minor blemish, but nothing is wasted.

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?

With an output schema present, return values need not be explained, and the description covers scope, non-recomputation of holdings, restrictions, and the correct alternative tool. It omits whether unrelated saved settings are preserved on partial updates and any blocking conditions, which would be expected for a destructive, nested-object mutation.

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 63%, and the description compensates by enumerating which of the 8 parameters are actually mutable, mapping 'include lists' and the Exclude list to their parameters. It does not add interpretation for locale or response_format, which stay schema-only, so it earns a 4 rather than a 5.

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?

States a specific verb (updates) plus the exact mutable fields (name, description, filter rules, include lists, exclude list) on one saved strategy, and explicitly distinguishes itself from acubic_create_strategy for structural changes. An agent can tell this apart from create/delete/restore siblings without opening a 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?

Gives an explicit when-not: ranking, weighting, limits and sizes cannot be changed here, and names the alternative (build a new strategy with acubic_create_strategy). It also adds a precondition-based restriction: a broker-connected strategy accepts name and description only.

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