Skip to main content
Glama

save_trading_config

Save the settings a run was started with as one of the person's trading configs.

    Saves what the person (or you on their behalf) set to start the
    run (ticker, indicator, conditions, risk settings). It shows under
    Trading configs in the Basic Strategies menu at the top of
    quanterlab.com, where the person can run it again.

    Useful AFTER you've validated a config (e.g. walk-forward looked
    good) so the user has it in their working library.

    It does not track the strategy live, and starts no paper trade:
    when the person asks to start it live, follow it or paper trade
    it, start_paper_trade does that, with a note on it every morning.

    Note: only saves for kinds that produce a deployable strategy
    (backtest, walkforward, stochastic_backtest, basic_backtest,
    regime_optimization). Scanner kinds (mr_scan, pairs_scan) don't
    have a config to save in this sense; save_workflow_result keeps
    their result instead.

    A rule that ran as a circuit of the lab's cards is kept as that
    circuit, with its report, under the report's name: `config_url`
    opens it in the lab, where it runs again as it ran.

    Args:
        task_id: The task_id returned by a prior `start_*` call.
        label: Optional human-readable label, max 100 chars.
    

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

Input Schema

NameRequiredDescriptionDefault
labelNo
task_idYes

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?

Beyond the annotations (readOnlyHint=false, idempotentHint=false), it discloses that no live tracking or paper trade starts, which kinds are unsupported, and that circuit runs are stored as a circuit with a report. It does not say whether re-saving the same task_id creates duplicates, which is the one gap for an idempotentHint=false mutation.

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?

Core purpose and the key exclusion are front-loaded in the first sentence. Most of the middle paragraphs earn their place, but the circuit paragraph is niche detail placed before the Args section, adding length for a two-parameter tool.

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 two-parameter, non-destructive save, it covers scope, exclusions, allowed kinds, and even mentions config_url for circuit runs. No output schema exists, yet the primary return surface (where the config shows up on quanterlab.com) is described, so an agent has what it needs.

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 0%, so the description carries the load: task_id is defined as coming from a prior start_* call, and label as optional, human-readable, max 100 chars. That covers both parameters with meaning the bare schema lacks, though the task_id format is not spelled out.

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?

Opens with a specific verb+resource: save the run's starting settings as a trading config, and clarifies the ticker/indicator/conditions/risk fields it captures. It explicitly differentiates itself from start_paper_trade and save_workflow_result, so an agent can pick it out of a large sibling list.

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-to-use (after validating a config, e.g. walk-forward looked good) and a when-not (person asks to go live/paper trade -> start_paper_trade). It also names save_workflow_result as the alternative for scanner kinds.

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