Skip to main content
Glama

create_sweep

Create the search, once the person has agreed to its size. The engine builds every candidate strategy itself out of the pool you give it -- the whole signal library unless narrowed by class or by naming signals -- and draws the parameters too. USE size_sweep FIRST and say the run count it reports: this call creates a draft and validates it, and a person who has not heard a total has not agreed to one. Still free; only launch_sweep spends. If valid comes back false, errors says why in Oracle's words, nothing was kept, and the fix is another attempt. Nothing runs until launch_sweep.

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": {
      "sweep_name": "<sweep_name>"
    },
    "name": "create_sweep"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetsNoAsset symbols, e.g. ["BTC", "ETH"].
regimesNoMarket conditions to keep: current, bear, neutral, bull. current means data within the last 30 days, which is recency and not direction. Omitted, every condition.
windowsNoSpecific window files to include whatever else is chosen.
categoriesNoDraw only from these signal classes, e.g. ["momentum"]. The classes are averaging, flow, momentum, oscillator, pattern and volatility. Omitted, the whole library.
sweep_nameYesWhat to call it.
candle_sizesNoCandle sizes, e.g. ["1h"]. Omitted, every size Oracle holds for those assets, which multiplies the windows.
exit_filtersNoDraw exit filters only from these.
entry_filtersNoDraw entry filters only from these. Omitted, every filter.
exit_triggersNoDraw an exit trigger only from these. Omitted, no exit signal is drawn at all and runs exit on the risk settings.
param_samplesNoHow many values each signal parameter contributes. The space is their product, so this is the dial that decides whether the search explores parameters at all; at 1 every candidate runs at a single setting.
signal_groupsNoKeep kinds of signal apart. A candidate draws ALL of its signals from ONE group, so two signals in different groups never appear on the same strategy. Runs are split across the groups.
entry_triggersNoDraw the entry trigger only from these signals, named as the knowledge graph registers them. Omitted, every trigger.
execution_baseNoRisk settings every run shares, from the execution config schema. Omitted, platform canon.
include_gappedNoInclude windows missing bars. Off by default, because a metric over a half-covered window is not comparable to one over a whole window.
max_total_runsNoA ceiling on the executed runs, applied by Oracle.
candidate_shapeNoHow many parts a drawn strategy gets, any of n_entry_triggers, min_entry_filters, max_entry_filters, min_exit_triggers, max_exit_triggers, min_exit_filters, max_exit_filters. Omitted, the platform default shape.
execution_sweepsNoExecution parameters to search too, each {param: {min, max, n}}. Every one of these multiplies the run count.
draws_per_datasetNoHow many candidate strategies to draw PER WINDOW. The runs that execute are this multiplied by the number of windows.
pre_filter_thresholdNoSkip a drawn candidate the SIEVE model predicts will not trade at all, above this confidence. A will-it-trade gate and nothing about whether it will make money. Omitted, no skipping.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Goes well past the annotations (readOnlyHint=false, destructiveHint=false) by disclosing that this call only creates and validates a draft, that it is free while launch_sweep spends, and that an invalid result keeps nothing and returns Oracle's error text. That is exactly the cost/side-effect/error context 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?

The critical instruction (size_sweep first, launch_sweep later) is front-loaded and the prose is dense rather than padded. The conversational asides ('a person who has not heard a total has not agreed to one') cost a little length for 19 parameters that could be trimmed, but nothing is truly wasted.

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 19-parameter, nested-object tool with no output schema, it covers cost, validation, failure semantics and the create/launch split. The one real gap is what a successful call returns (the sweep identifier needed to later launch or inspect it), which the agent must infer.

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 100% and the per-parameter text is already rich (e.g. param_samples and draws_per_dataset explain how run counts multiply), so the schema carries most of the load. The description still adds conceptual framing — the whole library is drawn unless narrowed by class or by name — which helps the agent reason about defaults, though it doesn't add per-parameter detail the schema lacks.

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?

Names a specific verb and resource ('Create the search' = draft sweep) and immediately scopes it: the engine generates every candidate strategy and its parameters from the pool supplied. It is clearly separated from size_sweep (sizing estimate) and launch_sweep (execution).

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?

Explicit sequencing: 'USE size_sweep FIRST', report the run count, then call this; 'Nothing runs until launch_sweep'. It also tells the agent what to do on failure ('the fix is another attempt'), so both when-to-use and when-not-to-use are covered.

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.