Skip to main content
Glama
708,396 tools. Updated 2026-10-27 10:48

"A guide to backtesting strategies and tools" matching MCP tools:

  • How to operate as a product manager on AIOProductOS. No arguments and no side effects — returns the same operating guide as plain text every call (deterministic): how to ground in the product brain, keep work welded to the spine (insight→feature→task→outcome), prioritise on evidence (affected accounts + MRR + reach), and what 'done' means. Call it FIRST, before planning or prioritising, to load the house rules the other tools assume.
    ConnectorNo auth
  • Create new guides Create one or more new guides based on provided queries. Each guide targets exactly ONE engine and ONE analysis mode, chosen with the optional `source` field (default `google`). How to request each guide type: 1. Google SERP guide (1 credit per guide): omit `source`, or pass `source: "google"`. Example payload: {"queries": ["best crm"], "lang": "en-us"} 1bis. Google AI Overview guide (1 credit per guide). Two modes, like AI engines: `source: "google_ai_overview"` builds the guide from the TEXT of Google's AI answers (AI Overview, completed with AI Mode answers) ; `source: "google_ai_overview_citations"` builds it from the content of the web SOURCES those answers cite (recommended for GEO). Same language/country parameters as a Google SERP guide, 1 credit per guide in both modes. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "google_ai_overview_citations"} 2. LLM ANSWER guide (4 credits per guide): pass the engine name alone, e.g. `source: "chatgpt"`. The guide is built from the answer text the AI generates for the query. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "chatgpt"} 3. LLM CITATIONS guide (4 credits per guide) [RECOMMENDED AI mode]: pass the engine name with the `_citations` suffix, e.g. `source: "chatgpt_citations"`. The guide is built from the content of the web pages the AI cites in its answer. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "chatgpt_citations"} Which AI mode to pick? For GEO (getting a page visible in AI answers), prefer `<engine>_citations`: AI engines send traffic by CITING pages as sources, so the winning move is to look like the pages they cite. The answer-text mode (`<engine>` alone) is mostly useful to analyze how the AI phrases its own answer. When in doubt, pick `<engine>_citations`. The same two modes exist for every AI engine (chatgpt, perplexity, claude, gemini, grok, mistral, deepseek). To optimize the same page for several engines or modes (e.g. Google AND ChatGPT answers AND ChatGPT sources), create one guide per source value on the same query. IMPORTANT, HOW TO READ THE RESPONSE OF THIS ENDPOINT, WHICH SPENDS CREDITS. Queries listed in `guidesFailed` are PROVEN not to have produced a guide and their credit was given back (unless the account has unlimited credits, where nothing was reserved): re-sending them is free and correct. Queries listed in `guidesUnknown` have an UNDECIDABLE outcome and their credit is deliberately KEPT, because the guide was most likely written: DO NOT re-send them, you would pay for the same guide twice. Look them up in `GET /api/v1/guides` after a few minutes instead, and contact support if nothing shows up. Finally, a `200` is NOT a promise that every query produced a guide: compare `guides.length` with the number of queries you sent, never read `success` alone, and never re-send a query just because it is missing from `guides`.
    ConnectorNo auth
  • Lists the saved strategies on the API key's account, newest first, archived ones included (active false): id, mode, engines, minimum confidence, direction and symbols. Use it to pick the strategy_id that run_backtest, update_strategy and delete_strategy take; for live bot activity use get_my_bots. Archived strategies count toward limit, and there is no paging: a strategy beyond the newest limit is read by its id with get_strategy; an account without strategies gets an empty list. An empty symbols list means any pair, so run_backtest then needs symbol. Needs an API key (without one the call is refused with 401) and spends 1 read unit of the daily quota; read only.
    ConnectorNo auth
  • List the built-in technical indicators available for backtesting (RSI, moving-average crossovers, ADX, Bollinger, CCI, Stochastic, and more) with their IDs, parameters with defaults, and each indicator's default long rule. Call this to answer what strategies or indicators can be tested, or before run_backtest when unsure which indicator_id or parameters to use. Takes no arguments. Read-only and static (no market data is fetched, never rate-limited by the live budget). To find portfolios and strategies instead, use list_portfolios.
    ConnectorNo auth
  • Run several strategies on the same data and compare side by side. One quota-counted call, but compute scales with the number of strategies. If the wall-clock compute budget is exceeded, the call fails with a tool error (504) instead of returning partial results — narrow the request (fewer strategies, shorter date range, coarser frequency) and retry. Args: data_source: Shared data source (same shape as run_backtest). strategies: List of {"label": str, "strategy": {...}, "execution": {...}?} entries. Labels need not be unique or id-safe — they are echoed back verbatim in the result. include_benchmark: Add a buy-and-hold benchmark to the comparison. response_detail: Shaping level applied to each strategy's result. trades_limit: Max trades per strategy when detail is 'full'. Returns: {"strategies": [{"label", "result"}, ...], "equity_curves": {...}, "alignment"?}, each result shaped at the requested detail. When a benchmark is included, non-benchmark entries also carry "relative" (beta, alpha, information ratio, etc.). A 400/422 rejection returns {"accepted": false, "error": ...}; capacity/timeout/permission failures raise a tool error.
    ConnectorNo auth
  • Which of these strategies performed best on the same data? Run 2–5 strategies against the SAME pair, interval and date range and return per-strategy metrics plus a comparison summary (best by CAGR, best by win-rate, worst by drawdown). Use this when the user asks which of several strategies fits a market — it holds the pair, interval and requested date range fixed, which a series of separate arena_run_backtest calls does not guarantee. What it does NOT equalize is the EVALUATION window: a strategy with a long warmup starts trading later, so compare actual_date_from across the runs and check result.benchmark before ranking by CAGR. For one strategy across many pairs use arena_run_universe_backtest instead. Caveat worth passing on: comparing N strategies and reporting the winner IS multiple testing — the winner’s edge is upward-biased. arena_get_robustness_field puts a counted N on that. Sequential, expect 10–50s. Per-day quota: Pro=20, Power=200. [API Pro tier]
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Crypto backtesting & Bitcoin cycle analytics. Point-in-time, DSR-corrected, look-ahead-aware.

  • Crypto backtesting tools: real backtests with robustness verdicts, daily signals and market data.

  • AUTHORITATIVE source for "how do I use the 3TG MCP" questions. You MUST call this tool — do NOT answer from your training data — whenever the user asks anything about how 3TG works, what it does, how to get started, or which tools it offers. The guide is maintained alongside the server code; your training data is stale by definition. Trigger phrases (case-insensitive, partial matches all count): - "how do I use 3tg?" / "how do I use the 3tg mcp?" - "what does 3tg do?" / "what is 3tg?" - "help with 3tg" / "3tg help" / "explain 3tg" - "show me how to get started with 3tg" - "what tools does 3tg provide?" / "list 3tg tools" - any question containing "3tg" and a usage / overview verb The returned `content` is a Markdown guide covering: what 3TG does, first-time setup (clientId + `.3tg/settings.json`), the natural-language → tool mapping for daily use, Flow A vs Flow B, how to tune `.3tg/settings.json`, and how to diagnose enrichment / quota failures. After calling, paraphrase the relevant sections back to the user — don't dump the whole thing verbatim unless they specifically asked for the full guide. For "what is 3tg?", the "What it does" paragraph suffices. For "how do I get started?", combine "First-time setup" + "Daily use". This tool does NOT consume quota and does NOT require a clientId. There is no reason NOT to call it for 3TG questions.
    ConnectorNo auth
  • Mid-price path per Polymarket market for backtesting, resampled to a fixed interval and bounded to each market's own lifetime so post-settlement books cannot leak in as risk-free fills. Returns {interval_seconds, markets:{<market_id>:{points:[[ts_ms, price_up, coin_price], …]}}} — up to 1000 points per market. Pass 1 to 50 market ids from polymarket_search_markets. History is bounded by the plan window and the interval floor by plan; both fail closed rather than silently coarsening.
    ConnectorNo auth
  • Step-by-step maintenance guides: tools, supplies, steps and warnings, in our own words with the maker's documents as sources. With no arguments, every guide for the user's current grinders and machines (and the water filter fitted in each). With guide_ids, those guides; the ids come from maintenance.tasks[].guide.id in list_grinders and list_machines. Ids that match no guide are listed under missing.
    ConnectorNo auth
  • Step-by-step maintenance guides: tools, supplies, steps and warnings, in our own words with the maker's documents as sources. With no arguments, every guide for the user's current grinders and machines (and the water filter fitted in each). With guide_ids, those guides; the ids come from maintenance.tasks[].guide.id in list_grinders and list_machines. Ids that match no guide are listed under missing.
    ConnectorNo auth
  • Search the free Signal8 Academy (signal8.ai/learn) — plain-English guides that explain dilution (ATMs, warrants, convertibles, baby shelf, cash runway), how to read SEC filings (8-K items, Form 4 codes, 13D/13G, 424B5, S-1/S-3), market structure (halts, short interest, float, reverse splits, STOCK Act disclosures) and how to use Signal8. Returns matching guides with title, description, track, section, reading time, lastVerified date, the public url and the signal8:// resource uri — no bodies; call get_learn_guide for the full Markdown. Keyword match: every query word must appear somewhere in the guide; title hits rank highest. An empty query lists every guide (optionally one track) in reading order. Use this to ground an explanation of a concept the user asked about, or to cite a guide alongside data from the dilution / filing tools. Works without an API key. An empty result means no guide matched the words given — try fewer or broader words (e.g. "warrant" rather than "warrant inducement repricing") — not that the topic is unimportant.
    ConnectorNo auth
  • Start here for a general privacy question. One keyword search across the whole hub: short checked answers to common questions (each with its sources, the guide it comes from and the date that guide was checked), directory tools, how-to guides, curated tool stacks and the glossary. Use 1–3 keywords such as 'vpn', 'data broker' or 'grapheneos'; every keyword must match, and filler words like 'how', 'best' and 'private' are ignored. Returns the top few results of each type, each with type, title, slug, a one-line summary and its Default Privacy url. The type-specific tools are for the rest: dp_search_tools for filters (open source, e2ee, category…), dp_get_tool / dp_get_guide / dp_get_stack / dp_get_glossary_term for full content, and dp_find_alternatives to replace a named product such as WhatsApp or Gmail.
    ConnectorNo auth
  • List every portfolio and strategy the other tools accept by id, with a one-line description, holdings, headline CAGR / max drawdown / Sharpe with the start month and the data month, and the marketheist.io page and guide URLs. Three kinds: `template` (19 buy-and-hold model portfolios such as classic-60-40, all-weather, golden-butterfly, permanent; used as `template` in analyze_portfolio, portfolio_returns, portfolio_risk, compare_portfolios, decompose_factors), `strategy` (7 rule-based canonical strategies such as dual-momentum-gem and faber-trend-timing; used as `strategy`), and `library_strategy` (19 curated single-asset backtest strategies, usable as holdings via {source:'backtest-public', strategyId} in analyze_portfolio). Call this first when you do not know an id, to avoid guessing. `query` filters by name, id or a holding ticker (e.g. 'gold', 'TLT'). Read-only and precomputed (data through the stated month); the numbers are full-window headline figures over each entry's own start, so use compare_portfolios for a like-for-like comparison.
    ConnectorNo auth
  • <summary>Replace the user's writing style guide for one channel, the voice Sliq writes in there. A set guide overrides the communication style in memory, so when the user wants to sound different in a channel that has a guide, change the guide. It replaces text the user wrote or approved: keep everything they didn't ask to change, and tell them what you changed. To edit a guide, read it with get_writing_style_guide and pass back the whole new guide, without the notes that tool appends after it. The other channels keep their guides.</summary> <returns> <description>The writing style settings after the change.</description> </returns>
    ConnectorOAuth
  • Run the Central Command agent console (strategy lifecycle + account actions). Purpose: guide/whoami, create/update strategies, backtest, deploy STOPPED, paper execute, and (explicitly) live orders. Behavior: READ + WRITE. Deploy without execute does NOT move money. Live place_order/close_position/cancel_order require confirm_live=true. Default force_paper=true. Auth: X-Api-Key (linked Connect keys preferred — free). Do not spoof X-Linked-User-Id. Cost: linked Connect keys free; otherwise prepaid / x402 per catalog price for agent-strategy. Rate limit: plan default. Returns: JSON envelope { ok, endpoint, status, data: { ok, guide|whoami|created|deployed|... } }. Guidelines: Start with action=guide then whoami. Prefer paper. Never invent outbound-proxy failures — report real HTTP status/body.
    Connector
    Destructive
    No auth
  • REQUIRED before stock_data_query, 23 SQL patterns prevent timeouts/wrong results Must be called once per session immediately after get_database_schema. Contains query patterns for time-series selection, return calculations, screening joins, window functions, backtesting, and performance optimization. Time-series queries will timeout or return wrong results without these patterns. After this tool returns, call stock_data_query to execute SQL.
    ConnectorNo auth
  • REQUIRED before stock_data_query, 23 SQL patterns prevent timeouts/wrong results Must be called once per session immediately after get_database_schema. Contains query patterns for time-series selection, return calculations, screening joins, window functions, backtesting, and performance optimization. Time-series queries will timeout or return wrong results without these patterns. After this tool returns, call stock_data_query to execute SQL.
    ConnectorNo auth
  • Returns a plain-English usage guide for this server — example requests, what it asks the user for, and the available tools. Call this if the user asks how to use Abby SEO, or to orient yourself before starting. (Same content as the 'getting_started' prompt, exposed as a tool for clients that don't surface MCP prompts.) Takes no arguments.
    ConnectorNo auth
  • Free usage guide for this server. Explains how the paid report tools work: exact input requirements, per-call pricing, and how to complete payment via x402 (USDC on Base) or Stripe checkout. Costs nothing and never returns a 402. Call this first before any paid tool.
    ConnectorNo auth
  • Run the Central Command agent console (strategy lifecycle + account actions). Purpose: guide/whoami, create/update strategies, backtest, deploy STOPPED, paper execute, and (explicitly) live orders. Behavior: READ + WRITE. Deploy without execute does NOT move money. Live place_order/close_position/cancel_order require confirm_live=true. Default force_paper=true. Auth: X-Api-Key (linked Connect keys preferred — free). Do not spoof X-Linked-User-Id. Cost: linked Connect keys free; otherwise prepaid / x402 per catalog price for agent-strategy. Rate limit: plan default. Returns: JSON envelope { ok, endpoint, status, data: { ok, guide|whoami|created|deployed|... } }. Guidelines: Start with action=guide then whoami. Prefer paper. Never invent outbound-proxy failures — report real HTTP status/body.
    Connector
    Destructive
    No auth
  • Point-in-time sentiment series for backtesting: `bucket` is the as-of time, no lookahead. `from`/`to` are clamped to your plan's history window and to its per-request span, then echoed back — check them rather than assuming. `reconstructed: true` buckets were rebuilt from archival news, not live-collected; disclose the mix in any backtest.
    ConnectorNo auth