Skip to main content
Glama

save_workflow_result

Save a finished run's result to the person's library on QuanterLab.

    The run is kept where the person finds it later, in the sidebar's
    Research Library on quanterlab.com, under Reports (one row with the
    report the run answered with):

      - a backtest, walk-forward, stochastic, basic or regime run, with
        its figures, trades, equity line and settings, opening as a full
        report;

      - a scan, with the names it passed and their settings.

    The run has to be finished: a save of a running task is refused
    with a message saying to wait for it.

    Args:
        task_id: The task_id returned by a prior `start_*` call.
        label: Optional name for the saved run, at most 100 characters.
            Without one it is named by its kind and stock ("Backtest on
            SPY, from an assistant"). A rule that ran as a circuit of the
            lab's cards is kept as its report, under the report's name.

    The answer carries `report_url`, the saved report's page, and
    `where`, the same place described in words (the sidebar's Research
    Library on quanterlab.com), for apps that rewrite links.
    

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

Input Schema

NameRequiredDescriptionDefault
labelNo
task_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only give generic hints (readOnlyHint=false, destructiveHint=false, idempotentHint=false); the description adds real value beyond them: exactly where the save lands (sidebar Research Library, under Reports), what is stored for each run kind, how default naming works, the 100-char label limit, and the failure mode for running tasks. This is the kind of persistence and error behavior annotations cannot convey.

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 destination, then structured bullets for the two run families, then args and returns. Slightly verbose in places (the 'where' phrasing is repeated), but every section carries information an agent needs.

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?

With no output schema, the description compensates by naming the response fields `report_url` and `where` and their meaning. Combined with the run-precondition and naming rules, an agent has everything needed to invoke this correctly and interpret the result.

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 description coverage is 0%, so the description carries the burden and largely meets it: `task_id` is explained as the id from a prior `start_*` call, and `label` gets a length cap plus the exact fallback naming convention. Minor gap: no stated format or example of what a task_id looks like.

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+resource ('Save a finished run's result') and the destination library, distinguishing it cleanly from the start_*/get_*_progress/result siblings that produce or inspect runs. An agent knows this is the persistence step, not the execution or retrieval step.

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?

Explicitly restricts use to finished runs and says a save of a running task is refused with a wait message, and it names `task_id` as coming from a prior `start_*` call. It stops short of naming the specific sibling progress tools an agent should poll first, so routing is implied rather than spelled out.

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