Skip to main content
Glama

start_mr_scan

Run QuanterLab's mean-reversion scanner across an index.

    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 scan takes about 30 seconds to 3 minutes. The call returns
    `{task_id, status, kind, dashboard_url}`; `get_mr_scan_progress(task_id)`
    reports progress and, when the scan has finished, carries `result`:
    each filter's rule as applied with how many names passed it, and up
    to ten names, those that passed every filter and then the closest
    misses, ranked, each with its own statistics rounded (`candidates`).

    `steps` is an ordered list of filters, each
    `{"type": ..., "params": {...}}`; a name has to pass a filter to reach
    the next. The filters and their settings, defaults in brackets:
        hurst           max_h, the highest Hurst exponent that passes [0.45];
                        window, bars [100]
        halflife        min_hl and max_hl, the half-life band in days [5, 100]
        adf             max_pvalue, the highest ADF p-value that passes [0.05]
        kpss            min_pvalue, the lowest KPSS p-value that passes [0.05]
        variance_ratio  max_vr, the highest variance ratio [0.95]; lag, bars [5]
        autocorr        max_acf, the highest lag-one autocorrelation [0.0]
        volatility      min_vol and max_vol, annual volatility as a fraction
                        [0.15, 0.60]
        liquidity       min_dv, average daily dollar volume in millions [10]

    Args:
        steps: The filters, in order (required).
        index: The universe: 'sp500', 'nasdaq100' or 'dowjones'. Asked for another index (the DAX, the
            FTSE 100), pass it all the same: QuanterLab answers with its note and the same scan on the S&P
            500, and nothing runs.
        timeframe: '1d' (daily bars, the only timeframe this connector runs).
        duration: The history: '6m', '1y' or '3y'.
        question: Optional. One sentence restating what the run should answer, not the person's
            message: the title of the report the finished run becomes, and kept only as that.

    When the run has finished, its answer also carries `report_url`: the scan written up as a QuanterLab
    report (the funnel and every name that passed). The call waits for the run while it is likely to finish
    inside it; the run's card in the chat shows the result or, for a longer run, how far it is, and fills in
    by itself, with the next steps as choices and the report link. A run started here needs no
    `show_report_card`.
    

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

Input Schema

NameRequiredDescriptionDefault
indexNosp500
stepsYes
durationNo3y
questionNo
timeframeNo1d

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations declare the safety profile (not read-only, non-destructive, non-idempotent, open-world); the description adds substantial context beyond that: a per-account daily allowance with refused calls not consumed, a 30s–3min runtime, the exact return shape `{task_id, status, kind, dashboard_url}`, and the fact that the call may block waiting for the run or hand off to progress polling. That is precisely the kind of behavior annotations cannot express.

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 purpose, then limits, then return behavior, then args — a sensible ordering, and the filter catalogue is justified by the untyped array with defaults that would otherwise be guesswork. Some tail material about the chat card filling in by itself and next-step choices is more verbose than the caller strictly 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?

No output schema exists, and the description nevertheless specifies both immediate returns and where `result`/`report_url` surface via get_mr_scan_progress. Combined with timing, quota behavior, and full parameter coverage, an agent has everything needed to call it correctly and interpret the outcome.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 full burden and does: it defines `steps` as an ordered filter list with per-filter parameter names, meanings and defaults (hurst, halflife, adf, kpss, variance_ratio, autocorr, volatility, liquidity), names the accepted `index` values and the out-of-universe fallback behavior, and constrains `timeframe` and `duration`. That is well beyond what the bare schema offers.

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 and resource: 'Run QuanterLab's mean-reversion scanner across an index.' The distinct resource name ('mean-reversion' / mr_scan) separates it cleanly from the many other start_* siblings (pairs, backtest, regime, walkforward) without needing to enumerate them.

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?

Establishes the usage context (a scanned index universe, with the daily allowance framing and 'a refused call does not count'), and points at get_mr_scan_progress as the natural follow-up. It also explicitly rules out a companion call ('A run started here needs no show_report_card'), which is real routing guidance. It stops short of an explicit when-not-to-use-this-vs-sibling comparison.

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