Skip to main content
Glama

Regenerate the suggested portfolio

acubic_regenerate_suggestion

Regenerates the suggested portfolio of one saved strategy with its saved settings, like Regenerate on acubic.ai, and returns the holdings and weights; the saved strategy is not changed. It never changes the ranking or the weighting: for another one, build with acubic_create_strategy. It counts against the same ranking and weighting attempt limit as the website.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "acubic_regenerate_suggestion"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoThe language of this conversation.
strategy_idNoThe saved strategy whose suggested portfolio is regenerated.
suggestion_idNoRead a suggestion still being computed (from a running result).
client_request_idNoIdempotency key.

Output Schema

NameRequiredDescriptionDefault
errorNo
methodNo
sourceNorescreen: the saved filters' re-screen; ranking: a fresh ranking; saved_names: the saved holdings re-weighted.
statusNo
droppedNoSaved holdings left out of the suggestion.
weightsNo
degradedNoTrue when the saved filters could not be checked: they were not applied and the saved holdings were kept (rescreen.status unavailable).
progressNo
rescreenNo
truncatedNo
cash_seatsNoSeats a saved correlation limit left empty, held as cash.
data_statusNo
strategy_idNo
suggestion_idNoWhile running: pass it back to read the suggestion.
weights_totalNo
correlation_limitNoPresent only when the saved correlation limit could not be met.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false with destructiveHint=false, and the description usefully clarifies that the stored strategy is untouched and that a ranking/weighting attempt is consumed — context the annotations do not carry. It does not, however, explain whether a new suggestion record is persisted, whether regeneration is repeatable, or how the attempt limit is counted or reset.

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 action and the outcome, then the constraint, then the cost caveat; no filler sentences. The first sentence is long and packs return value, invariance, and sibling routing together, which slightly reduces readability.

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, the description need not explain return values, and it still names them; annotations cover the safety profile and the description adds the attempt-limit behavior. Remaining gaps (idempotency given idempotentHint=false and a client_request_id parameter, and what happens on repeated calls) are minor but real.

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%, so locale, strategy_id, suggestion_id, and client_request_id are all documented in the schema; the description adds no per-parameter meaning. "With its saved settings" implicitly explains why no weighting/ranking parameters appear, which is marginally useful, so baseline 3 applies.

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 ("Regenerates the suggested portfolio of one saved strategy"), notes the saved settings used, describes the return ("returns the holdings and weights"), and explicitly scopes the effect ("the saved strategy is not changed"). An agent can distinguish this from acubic_create_strategy without opening either schema.

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 names an alternative and a condition for choosing it ("for another one, build with acubic_create_strategy") and adds a cost caveat about the attempt limit shared with the website. The phrase "for another one" is slightly ambiguous about whether it means another portfolio or another strategy, so routing is clear but not airtight.

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