Skip to main content
Glama

Create a strategy

acubic_create_strategy

Creates and saves a new draft strategy from the acubic.ai builder's choices: universe, include lists, asset count, sizes, ranking, weighting, filter rules, limits, and tickers to add, exclude or lock. A preset (template_id) fixes the menu; without one every engine argument is open. It uses one portfolio generation from the plan's allowance; with a candidates_id from acubic_rank_candidates it saves that pick at no generation cost. A saved strategy keeps its method: to try another, build again (see allocation); acubic_regenerate_suggestion does not change it. May return a build_id for acubic_get_build_status. To edit one use acubic_update_strategy. Always show the automation.url it returns (automate on acubic.ai).

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

Input Schema

NameRequiredDescriptionDefault
nameYes
localeNoThe language of this conversation.
includeNoIds per acubic_list_strategy_options section (index: indices).
rankingNoA preset: card (its menu: acubic_list_strategy_templates). The engine: rank_method or rank_blend.
regionsNo
sectorsNo
recipe_idNoA recipe id (acubic_list_strategy_options, recipes): sets ranking, sectors, allocation and asset count unless given; your filter_rules add to its own.
allocationNoWeighting id (acubic_list_strategy_options, weighting); default: the recommended one. To compare: acubic_rank_candidates once, then this tool with its candidates_id and each allocation in turn.
experienceNoLegacy: beginner or intermediate with risk_level selects a preset; prefer template_id. Omit for an engine build.
index_cardNoBuild the level's index card (template level_mix.index_card) instead of ranked stocks; no ranking or allocation.
risk_levelNoPreset only (legacy path): largest acceptable drawdown; prefer template_id.
asset_countNoNumber of assets.
descriptionNo
template_idNoAn id from acubic_list_strategy_templates: a preset, or advanced for the engine.
filter_rulesNoEach rule: metric, op, value in the metric's unit (US dollars for market_cap, percent for pct metrics: 40 = 40%).
select_countNoTop N to select (10, 15, 20, 30 or 50 within the count range; see selection.select_counts). Not with selected_symbols.
asset_classesNo
candidates_idNoA ranked list from acubic_rank_candidates (valid 1 hour).
custom_symbolsNoTickers to add to the pool, checked as on acubic.ai.
locked_symbolsNoAlways held, exempt from every filter.
position_sizingNoDefault: the sizes recommended for the number of assets.
response_formatNoconcise
excluded_symbolsNoNames removed from the screened pool (Step 1).
selected_symbolsNoHand-picked names of the candidates_id list (not with allocation or correlation limits).
selection_limitsNoMin/max share of the selection per sector, country or asset class.
asset_count_rangeNoInstead of asset_count (default 15 to 25).
client_request_idNoIdempotency key.
correlation_limitNoNot offered yet: omit it unless acubic_list_strategy_options shows it offered; then 0.50-0.95, step 0.05 (preset: 0.80).
class_position_sizingNoPer-asset-class sizes overriding position_sizing.

Output Schema

NameRequiredDescriptionDefault
errorNo
quotasNo
statusNo
build_idNoPresent while running; accepted by acubic_get_strategy.
holdingsNo
progressNo
strategyNo
selectionNo
truncatedNo
automationNo
disclosureNo
generationNo
strategy_idNoSet only with detail_unavailable.
custom_symbolsNo
holdings_totalNo
client_request_idNoThe idempotency key this call used (yours, or one made for it). Repeat the call with it to get the same run without a second charge.
quota_unavailableNoTrue when the quota counters could not be read after the work was saved; the work is saved.
detail_unavailableNoTrue when the saved work could not be read back just now; the work is saved.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing allowance consumption (one portfolio generation), the zero-cost candidates_id path, immutability of a saved strategy's method, a possible build_id return, and the requirement to show automation.url. The only residual gap is that the presence of client_request_id alongside idempotentHint=false is not reconciled, leaving retry behavior slightly ambiguous.

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?

Front-loaded with the core action and the cost model, and every clause carries operational meaning. It is densely packed with parenthetical cross-references to other tools, which makes it harder to scan than it could be, but there is no filler.

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 29-parameter tool with nested objects and an output schema, the description supplies exactly what the schema cannot: preset vs engine mode, generation cost accounting, method immutability, and the follow-up tool for build status. Return values are covered by the output schema and correctly not repeated.

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 high (79%) so the schema carries most parameter detail, but the description adds the governing distinction between preset-fixed and open engine arguments that no single parameter description conveys. It also flags that candidates_id is time-limited and that correlation_limit should be omitted unless offered, adding meaning beyond the field docs.

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 and resource ("Creates and saves a new draft strategy") and immediately enumerates the builder inputs it consumes. It explicitly separates itself from siblings: acubic_update_strategy is named for editing, acubic_regenerate_suggestion is named as not modifying a saved strategy, and candidates_id is tied to acubic_rank_candidates.

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 explicit routing conditions: use a preset (template_id) to fix the menu, otherwise the engine arguments are open; to change a saved strategy's method, build again rather than regenerate; to edit, use acubic_update_strategy. It also states the cost trade-off that selects the candidates_id path (no generation charge).

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