Skip to main content
Glama

start_primitives_run

Run one of your saved lab projects (a circuit on the canvas, its latest version) and return a task id to poll. The project runs as saved, at its point-in-time anchor, and takes no settings but index. Its card draws the project's own circuit as the lab draws it, lights each card as it runs and shows the result under it. Get a project id from list_my_primitives_projects, then poll get_primitives_run_progress: when the run has finished its answer carries result, each branch of the project under the card name the project gives it, whether it beat simply holding what it trades over the same dates, and, for a branch tested over a year or longer, a few rounded figures.

    Every account runs it within a daily allowance; a refused call does not count, and get_started and
    every run's answer give today's count.
    A paper-trade card runs as a marker in the test; start_paper_trade with the run's task_id tracks the
    project live, on paper, with a note on it every morning.

    The circuit and its settings stay on QuanterLab. This run's curves are in its report
    (`report_url`, below); `result.lab_url` opens the project on the canvas, where the person
    changes it and saves it.

    When the run has finished, its progress answer also carries `report_url`: the run written up
    as a QuanterLab report (the circuit drawn, each branch that trades against simply holding and
    SPY, and what followed each event of an event-study card). The circuit card shows the result
    under the circuit, with the next steps as choices and the report link, so a run started here
    needs no `show_report_card`.

    Args:
        project_id: The `id` of one of your saved lab projects.
        question: Optional. One sentence restating what the run should answer, not the person's message:
            the title of the report, and kept only as that.
        index: Optional. sp500, nasdaq100 or dow30: the project's cards that pick their stocks from an
            index QuanterLab has today's members of only (the DAX, the CAC 40, the FTSE 100, the EURO
            STOXX 50, the Hang Seng, the Nikkei 225) pick from this US index instead, its members as they
            were on each date, for this run only; the saved project is left as it is. QuanterLab's note
            offers it after such a run.
    

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

Input Schema

NameRequiredDescriptionDefault
indexNo
questionNo
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety and mutability profile is covered. The description adds real context beyond that: a daily allowance with refused calls not counting, the saved project being left unchanged when `index` overrides the universe, and where the output lives (report_url, result.lab_url). That is useful but sits at the level of extra context rather than disclosing anything the annotations miss about failure modes or timing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core action and the poll-next instruction are front-loaded, which is right. But the description is bloated with card-rendering prose ('lights each card as it runs and shows the result under it') and explains report_url twice in two separate paragraphs, adding length without adding decision-relevant information.

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 takes on the return-value burden and meets it: it names the task id, the `result` payload with per-branch performance vs holding, `report_url`, and `result.lab_url`. Combined with the allowance note and the paper-trade handoff, an agent has everything needed to call it 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 full burden and largely does: `project_id` is tied to `list_my_primitives_projects`, `question` is constrained to one sentence and used only as the report title, and `index` is given its three accepted values (sp500, nasdaq100, dow30) plus the override semantics. The `index` explanation is long and hard to parse, and the fact that the values are not an enum in the schema makes the description the only guard against invalid input, so it is good but not airtight.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: run a saved lab project and return a task id to poll. It clearly scopes the resource as an already-saved project that runs as-is at its point-in-time anchor, which separates it from the ad-hoc circuit/backtest starters. It does not explicitly name run_circuit or start_backtest as the alternatives an agent might confuse it with, so sibling differentiation is only partial.

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 workflow: get the `id` from `list_my_primitives_projects`, then poll `get_primitives_run_progress`. It names `start_paper_trade` as the follow-on path with the run's task_id, and states a run started here needs no `show_report_card`, which is exactly the kind of exclusion an agent needs.

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