quantifyme

Quality 66 / 100needs work

13 tools, about 4,312 tokens to load them all · tool set 683d409dd36b · tools last changed 2026-10-11 · checked 2026-10-19 10:52 UTC

Tool changes

• 2026-10-11list_modelschangeddescription
  before

  List the user's trained models with pre-computed train/test stats.

  after · 52% of words in common

  List the user's trained models with pre-computed train/test stats. `acting_as` names the identity listed: the linked account or a trial user (#1962).

• 2026-10-11link_accountchangeddescription
  before

  Link this chat to the user's existing QuantifyMe account. Call this when the user says they already have a QuantifyMe account, or asks why their models are missing / where a model went, or wants what they deploy here to show up in their own dashboard. By default this connector works with NO signup: it mints an anonymous trial account per chat, so models deployed here belong to that throwaway identity rather than to the user's real one. This returns a short-lived URL; once the user opens it and approves, every later call in THIS chat acts as their account and deploys land in their own model list. Give the user the `link_url` to open. Nothing else is required from them.

  after · 82% of words in common

  Link this chat to the user's existing QuantifyMe account. Call this when the user says they already have a QuantifyMe account, or asks why their models are missing / where a model went, or wants what they deploy here to show up in their own dashboard. By default this connector works with NO signup: it mints an anonymous trial account per MCP session, so models deployed here belong to that throwaway identity rather than to the user's real one. This returns a short-lived URL; once the user opens it and approves, every later call that carries the same OAuth bearer or the same MCP session acts as their account and deploys land in their own model list. A client that opens a new MCP session on every turn must link again in that session; every answer's `acting_as` line says which identity was used. Give the user the `link_url` to open. Nothing else is required from them.

• 2026-10-05stream_testchangeddescription
  before

  Diagnostic: test whether LIVE data streaming works in this client. Renders a widget with three panels — a JS timer (baseline), a WebSocket to the live price feed, and an HTTP poll of /quote — each showing a live value + status, so you can see exactly which streaming mechanisms the client's widget sandbox actually permits. Use when a live/ticking chart isn't moving. Args: symbol: G7 pair to stream (default EURUSD).

  after · 84% of words in common

  Diagnostic: test whether LIVE data streaming works in this client. Renders a widget with three panels: a JS timer (baseline), the WebSocket panel (not offered: the feed needs a credential and none is sent to a widget), and an HTTP poll of /quote, each showing a live value + status, so you can see which streaming mechanisms the client's widget sandbox permits. Use when a live/ticking chart isn't moving. Args: symbol: G7 pair to stream (default EURUSD).

• 2026-10-05find_strategychangeddescription
  before

  Find an existing PROVEN strategy that matches a plain-English idea, so you can offer the user a choice — deploy the existing one, or generate a fresh custom one. Mirrors the quantifyme.ai landing experience: "Found <X> by @<author> (WR/PF) — Use it / Generate fresh". CALL THIS FIRST when a user describes a strategy idea. Then present the match (if any) and ASK which they want: • Use it → one_shot(community_id=<match.community_id>) — deploys the exact proven strategy (free, no generation). • Generate fresh → one_shot(prompt="<their description>") — Claude writes a brand-new custom strategy for them. If there's no match, just offer to generate fresh. Args: description: the user's strategy idea in plain English (e.g. "buy EURUSD 15min when RSI < 30, sell when RSI > 70"). symbol: optional pair to constrain the match (EURUSD, USDJPY, GBPUSD, USDCHF, USDCAD, AUDUSD, NZDUSD). timeframe: optional granularity to constrain the match (1min/5min/15min/1h). Returns: dict with: - match: the best existing strategy, or null. When present: {community_id, title, username, wr, pf, ret, n_trades, symbol, timeframe}. Pass community_id to one_shot to deploy it unchanged. - description: echoed back — pass as one_shot(prompt=...) to generate fresh. - suggestion: a ready-to-show sentence offering the user the choice.

  after · 81% of words in common

  Find an existing PROVEN strategy that matches a plain-English idea, so you can offer the user a choice — deploy the existing one, or generate a fresh custom one. Mirrors the quantifyme.ai landing experience: "Found <X> by @<author> (WR/PF) — Use it / Generate fresh". Use this when a user wants to browse for an existing strategy. A vague deploy request does NOT need it: one_shot(prompt=...) deploys the best curated preset or a fresh build. A community strategy is another user's code, so it deploys only after the user has seen its author and code (get_strategy_code with the match's community_id) and picked it. Present the match (if any) and ASK: • Use it → one_shot(community_id=<match.community_id>) — deploys the exact strategy they picked (no generation). • Generate fresh → one_shot(prompt="<their description>") — Claude writes a brand-new custom strategy for them. If there's no match, just offer to generate fresh. Args: description: the user's strategy idea in plain English (e.g. "buy EURUSD 15min when RSI < 30, sell when RSI > 70"). symbol: optional pair to constrain the match (EURUSD, USDJPY, GBPUSD, USDCHF, USDCAD, AUDUSD, NZDUSD). timeframe: optional granularity to constrain the match (1min/5min/15min/1h). Returns: dict with: - match: the best existing strategy, or null. When present: {community_id, title, username, wr, pf, ret, n_trades, symbol, timeframe}. Pass community_id to one_shot to deploy it unchanged. - description: echoed back — pass as one_shot(prompt=...) to generate fresh. - suggestion: a ready-to-show sentence offering the user the choice.

• 2026-10-05top_upchangeddescriptionmeaning changed
  before

  Fund your QuantifyMe credits with crypto (USDC) — no signup, no human, no card. The agent-native funding rail. SIMULATED in this build (no real charge) and capped at $100 for the POC. Returns your new credit balance.

  after · 25% of words in common

  Simulated crypto top-up for a QuantifyMe DEV server only: no money moves, so it never makes an account paid and grants at most up to the free credit cap ($100 per call). quantifyme.ai refuses it (#1098) and answers with how to pay for real: send USDC on Base to your deposit address (GET /api/v1/wallet/deposit_address). Returns your new credit balance.

• 2026-10-05get_deploy_resultchangeddescription
  before

  Wait for a `one_shot` deploy to finish and return its final result. `one_shot` returns a job_token immediately and the LIVE CARD already streams progress and renders the interactive backtest chart itself. Call this ONCE with the token to get the final numbers as TEXT so you can summarize them — it does NOT render another card (no need for get_model_chart). It BLOCKS until the deploy finishes (or ~2.5 min); on timeout it returns ok:false + pending:true — call it again with the same token. IMPORTANT: if `source == "community"`, the deploy used a PRE-EXISTING strategy by `@author` — tell the user that, share the `live_url` as the Live dashboard link, and ask whether they'd like to GENERATE A CUSTOM strategy instead. Use the `note` field as your guide. Args: job_token: the token returned by `one_shot`. Returns: dict with: ok, stem, model, live_url, symbol, timeframe, channels (list), stats:{ret, wr, pf, n, mdd} (out-of-sample test-split metrics — SHOW THESE), source ("community" | "generated"), author (community username if any), author_url + strategy_url (render @author and "pre-existing strategy" as those Markdown links), community_id, suggest_custom (bool), and note (a ready instruction — follow it). On failure: {ok:false, error} (or {pending:true}).

  after · 88% of words in common

  Wait for a `one_shot` deploy to finish and return its final result. `one_shot` returns a job_token immediately and the LIVE CARD already streams progress and renders the interactive backtest chart itself. Call this ONCE with the token to get the final numbers as TEXT so you can summarize them — it does NOT render another card (no need for get_model_chart). It BLOCKS until the deploy finishes (or ~2.5 min); on timeout it returns ok:false + pending:true — call it again with the same token. IMPORTANT: if `source == "community"`, the deploy used a PRE-EXISTING strategy by `@author` (the user picked it) - tell the user that, share the `live_url` as the Live dashboard link, and ask whether they'd like to GENERATE A CUSTOM strategy instead. A `suggestion` is a community strategy that matched a vague request; it was NOT deployed; offer it, and deploy it only after the user sees its author and code and picks it. Use the `note` field as your guide. Args: job_token: the token returned by `one_shot`. Returns: dict with: ok, stem, model, live_url, symbol, timeframe, channels (list), stats:{ret, wr, pf, n, mdd} (out-of-sample test-split metrics — SHOW THESE), source ("preset" | "generated" | "community"), author (community username if any), author_url + strategy_url (render @author and "pre-existing strategy" as those Markdown links), community_id, suggest_custom (bool), suggestion ({community_id, title, author} or null: offered, not deployed), and note (a ready instruction - follow it). On failure: {ok:false, error} (or {pending:true}).

• 2026-10-05one_shotchangeddescription
  before

  End-to-end deploy: generate strategy → train → deploy live. One of `prompt` (free-form NL), `preset` (curated winning strategy), or `community_id` (copy a published community strategy) is required. If more than one is passed, precedence is community_id > preset > prompt. Args: prompt: Natural-language strategy description (e.g. "Buy when RSI < 30, sell > 70"). symbol: Currency pair to backtest on. One of: EURUSD, USDJPY, GBPUSD, USDCHF, USDCAD, AUDUSD, NZDUSD. Default EURUSD. timeframe: Candle granularity. One of: 1min, 5min, 15min, 1h. Default 15min. claude_model: Which Claude variant to use for code generation. "sonnet" (default — best quality, 1/day free) or "haiku" (faster, 3/day free). Ignored when `preset` is set (no generation needed). preset: Curated winning-strategy slug. Skips Claude generation entirely — deploys a pre-saved strategy known to backtest well on the chosen symbol. Available slugs: ema_cross_fast, momentum, scalper_stack, sma_only, trend_ema, volatility, bb_squeeze, all_mix, pivot_kid_ema. Not every slug exists for every symbol — call list_models afterwards to confirm what deployed. community_id: Copy-trade a published community strategy. Pass the `id` of an entry from `browse_community`. Loads that exact strategy code, skips Claude generation, then trains + deploys it. `symbol`/`timeframe` still apply to the backtest+deploy. webhook_url: Optional webhook to receive live signals. telegram_chat_id: Optional Telegram chat ID for signal delivery. Returns IMMEDIATELY (the deploy runs in the background so the live card can stream progress) with: - job_token (str): pass to get_deploy_result to fetch the final result. - poll_url (str): the card polls this for live progress; you can ignore it. - pending (bool): always true here — the deploy is still running. - symbol, timeframe (str). Call this EXACTLY ONCE per request. Pass the user's words as `prompt`; do not pre-pick presets/community strategies — the server routes (vague → a proven community strategy, specific rules → a fresh generation). NEXT STEP (always): call get_deploy_result(job_token) ONCE — it blocks until the deploy finishes and returns the out-of-sample stats + `stem` + `source`/`author` as TEXT so you can summarize. The live card already shows the chart, so you do NOT need get_model_chart. If source='community', tell the user it used a pre-existing strategy by @author and offer to generate a custom one.

  after · 94% of words in common

  End-to-end deploy: generate strategy → train → deploy live. One of `prompt` (free-form NL), `preset` (curated winning strategy), or `community_id` (copy a published community strategy) is required. If more than one is passed, precedence is community_id > preset > prompt. Args: prompt: Natural-language strategy description (e.g. "Buy when RSI < 30, sell > 70"). symbol: Currency pair to backtest on. One of: EURUSD, USDJPY, GBPUSD, USDCHF, USDCAD, AUDUSD, NZDUSD. Default EURUSD. timeframe: Candle granularity. One of: 1min, 5min, 15min, 1h. Default 15min. claude_model: Which Claude variant to use for code generation. "sonnet" (default — best quality, 1/day free) or "haiku" (faster, 3/day free). Ignored when `preset` is set (no generation needed). preset: Curated winning-strategy slug. Skips Claude generation entirely — deploys a pre-saved strategy known to backtest well on the chosen symbol. Available slugs: ema_cross_fast, momentum, scalper_stack, sma_only, trend_ema, volatility, bb_squeeze, all_mix, pivot_kid_ema. Not every slug exists for every symbol — call list_models afterwards to confirm what deployed. community_id: Copy-trade a published community strategy. Pass the `id` of an entry from `browse_community`. Loads that exact strategy code, skips Claude generation, then trains + deploys it. `symbol`/`timeframe` still apply to the backtest+deploy. webhook_url: Optional webhook to receive live signals. telegram_chat_id: Optional Telegram chat ID for signal delivery. Returns IMMEDIATELY (the deploy runs in the background so the live card can stream progress) with: - job_token (str): pass to get_deploy_result to fetch the final result. - poll_url (str): the card polls this for live progress; you can ignore it. - pending (bool): always true here — the deploy is still running. - symbol, timeframe (str). Call this EXACTLY ONCE per request. Pass the user's words as `prompt`; do not pre-pick presets/community strategies - the server routes (vague → the best curated preset for the market, or a fresh build when there is none; specific rules → a fresh generation). A community strategy deploys only after the user has seen its author and code (get_strategy_code) and picked it: then pass its `community_id`. NEXT STEP (always): call get_deploy_result(job_token) ONCE — it blocks until the deploy finishes and returns the out-of-sample stats + `stem` + `source`/`author` as TEXT so you can summarize. The live card already shows the chart, so you do NOT need get_model_chart. If source='community', tell the user it used a pre-existing strategy by @author and offer to generate a custom one. If the result carries a `suggestion`, you may offer that community strategy.

Full history: list_changes · trend: quality JSON.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.