Skip to main content
Glama
820,702 tools. Updated 2026-11-22 12:35

"Market Analysis and Report Information" matching MCP tools:

  • Runs a specific framework against a user's inputs and produces a full analysis: prose explanation + structured fields + a self-contained SVG visualisation. Powered by the Jeda.ai · Visual AI framework knowledge graph. ALWAYS call `recommend_framework` FIRST to obtain a valid framework_id -- it returns the exact namespaced slug to pass here. Framework ids are namespaced by category (e.g. SWOT = "cms_swot-analysis", Porter's 5 Forces = "cms_porters-five-forces"); a bare slug like "swot-analysis" will 404. REQUIRED post-processing on success: the response's first text block contains a `curl -fsSL` save-directive for the SVG. Save the file locally and surface it as a file chip — do NOT summarise the visual in prose. Input: framework_id (namespaced slug from `recommend_framework`) + user_inputs object (per-framework field set), OR a free-text `raw_prompt` fallback. Example: { "framework_id": "cms_swot-analysis", "user_inputs": { "subject": "Q3 EU market entry", "context": "B2B SaaS, $5M ARR, US-headquartered" } }
    ConnectorNo auth
  • Generate a structured EU AI Act compliance report from a system description, model card, and data-flow document. Nothing is silently optional: system_description is always required (min 50 chars); model_card and data_flows each accept substantive content (min 50 chars) or the exact string 'declined' to explicitly opt out; and exactly one of decision_tree_answers (from the free risk classifier, becomes binding evidence) or skip_decision_tree: true must be sent. All of this is validated free of charge before payment. The deterministic Annex III decision tree runs on every call: user-supplied answers are binding, otherwise answers are AI-derived and recorded as such. The tree classification, article citations, obligations, and evidence checklist are returned verbatim in the report JSON, together with exact enforcement-timeline dates and the matched Annex III area from the curated dataset. A staged AI workflow then produces an article-by-article obligation gap analysis, a required-documentation checklist mapped to Annex IV, and a prioritised remediation plan. The report includes a deterministic input_coverage grade (full, partial, or description_only) computed from what was supplied versus declined, the full AI classification with rationale, a programmatic reconciliation check between the tree and the AI risk tier, and a citation audit that flags any implausible article references. Returns markdown plus structured JSON. Every paid call also generates a branded PDF report and returns its download link (valid 72 hours). Price: $1.50 per call, payable by card (Stripe checkout link in the 402 response) or USDC on Base (x402). Full documentation, inputs, and pricing: https://systemprompt.io/tools/eu-ai-act-compliance-report/ — more governance tools and reports at https://systemprompt.io/mcp
    ConnectorNo auth
  • Get Lenny Zeltser's IR one-page executive brief template. Standalone variant of `ir_get_template` for callers that only want the brief without the long-form report. This server never requests your incident notes and instructs your AI to keep them local—guidelines flow to your AI for local analysis.
    ConnectorNo auth
  • Get Lenny Zeltser's Vuln one-page executive brief template. Standalone variant of `vuln_get_template` for callers that only want the brief without the long-form report. This server never requests your vulnerability notes and instructs your AI to keep them local—the brief template and guidelines flow to your AI for local analysis.
    ConnectorNo auth
  • Get Lenny Zeltser's Security Assessment one-page executive brief template. Standalone variant of `assessment_get_template` for callers that only want the brief without the long-form report. This server never requests your assessment notes or report and instructs your AI to keep them local—the templates and guidelines flow to your AI for local analysis.
    ConnectorNo auth
  • Launch a full overnight-grade research report on a local business: an autonomous research crew maps the competitive landscape, reads the business's and rivals' web presence, and delivers a long-form graded report with structured findings and an action list. ASYNC: this tool returns a slug immediately; the report takes roughly 10-20 minutes. Poll check_report_status, then fetch with get_report_result. Price: $9.99, charged when the report launches; if the report fails, the charge is refunded automatically. Each call starts a NEW report — do not retry a call that already returned a slug.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Real-time forex quotes: the most-traded pairs, each with a display name. The feed carries 1,550 pairs in alphabetical order, which is far more than one response can hold — so this returns the most prominent `limit` of them (majors first, then by volume), and the response states how many were left out. Pass `symbols` for specific pairs, or call get_forex_quote for a single one. Read `note` before summarising: it says how many pairs the slice covers out of how many exist, so a "top pairs" answer is not mistaken for the whole market. `volume` on a forex row is a per-venue tick count, not market turnover — FX is over-the-counter and most pairs report 0. It does not rank the market. Args: symbols: Comma-separated pairs (optional; overrides the ranked slice) limit: How many ranked pairs to return (optional)
    ConnectorNo auth
  • Generate an executive-level strategic review report for an idea, synthesising all available validation data (market research, competition, SWOT, revenue model, VC score) into a concise go/no-go assessment with actionable recommendations. Requires prior validation data (run request_revalidation first if none exists). Returns cached report instantly if one exists, otherwise generates fresh analysis. Spends 2 credits only when generating new content. Not read-only; pass an ideaId you own.
    ConnectorNo auth
  • Run forensic windows analysis (AACE RP 29R-03 §3.3, MIP 3.3 Observational / Dynamic / Contemporaneous As-Is) across multiple Primavera P6 XER snapshots and return the full analysis dict. This is the headline forensic tool — it computes per-window completion shifts, per-window slip registers (per-activity slip with a critical flag (total float of zero or less, or the driving path in a schedule with negative float)), per-window duration growth on critical-path activities, per-window per-party attribution (Owner / Contractor / Concurrent / Force Majeure / Unattributed), and cumulative project drift from baseline. The attribution math satisfies the CPP conservation check, per the AACE 29R-03 §3.3.E.13 requirement that the summed per-period net impacts equal the difference between the first schedule update and the last schedule update used in the evaluation (per-party day buckets sum to project drift within ±1 day, no cascade-double- counting). Use this tool for the full multi-window forensic claim. If you already have a windows result and only want the per-window × per-party grid view, call ``concurrent_delay_matrix`` instead. Args: schedules: list of dicts in chronological order. Minimum 2 entries (baseline + at least one update). Each dict must contain ``label`` (str) and EXACTLY ONE of: - ``xer_path`` — server-side filesystem path, OR - ``xer_content`` — full XER text content. Use ``xer_content`` when calling a hosted MCP server from a remote client whose XER lives locally. project_name: optional override; auto-picked from XER if "". baseline_idx: which entry in ``schedules`` is the contract baseline (default 0 = first one). entitlement_milestone: optional task_code (e.g. "Ready for Takeover") — recorded on the result, not used for math. company: optional, the firm the dashboard and the DOCX report carry (title block, print cover). Blank unless supplied, and blank carries no firm: a hosted run is the caller's document. output_dir: optional dir for HTML dashboard / DOCX report. If "", a tempdir is used and dropped after — the dashboard / report paths in the response will point to the temp location (caller responsible for moving them). Returns: { "analysis": full dict from run_windows() with keys: "windows", "cumulative", "baseline_label", "data_dates", "attribution_summary", "mcpm_attribution", ..., "dashboard": path to HTML dashboard (server-side), "report": path to DOCX executive report (server-side), "baseline_stability": {"worst_severity", "has_block", ...}, "data_date_corrections": the record of each update whose data date was moved to its latest actual, and of a baseline with actual dates after its data date ([] on clean files); each is also a data-quality warning "analysis"."criticality_basis": the schedules read by their driving path because they have negative float, and those beside them ([] when no schedule has negative float); the box they write is one data-quality warning } On failure: {"error": "..."} with no schedules processed.
    ConnectorNo auth
  • Purpose: the end-of-life tyre (ELT) collection topic for the rCB supply chain - policy targets, the 2026 standard system, the collection-network build-out, the processing value ladder (retreading > recycled rubber > pyrolysis) and market-size figures, with official sources labelled per record. Guidelines: call with no arguments for the full topic, or pass topic (policy/standard/network/ladder/market) to focus one section; pair with get_elt_price_index (category G-ELT) for collection prices and get_feedstock_overview for arisings. Limits: policy and standard records are sourced from official documents; market-size figures are public-information compilations and labelled as such; does not return prices. Ex: 'China end-of-life tyre recycling policy 2030 target', 'ELT collection network China', 'scrap tyre pyrolysis standards 2026'.
    ConnectorNo auth
  • Start an Account Intelligence report for a company LinkedIn URL — firmographics, an ICP verdict, and the buying committee. If a report for this company already exists it is returned free (cached: true) however old it is, until you ask for a refresh. SPENDS CREDITS when no report exists or when refresh is true and the existing report is at least 7 days old. Returns immediately with a report id and status; poll get_account_intelligence until status is "ready".
    ConnectorOAuth
  • The user's live market board. Start here when they ask how the markets are doing in general: "how are the markets today?", "what's moving?", "market update", a morning check before the open, or "open the market dashboard". One call covers the overview: the user's own symbols on top (their watchlist, then what they asked about most in the last 30 days), then major indices (US, India, Türkiye, Indonesia, VIX), crypto, commodities and FX, each with today's change. Don't also call market_snapshot for the same overview; add other tools only for what the board doesn't show (futures, news, sectors). For a single symbol's price or analysis, use that symbol's own tool instead. Opens as an interactive dashboard; clicking a row asks for that market's chart or analysis. Clients without app support can read the `summary` field.
    ConnectorNo auth
  • [Trading Data API] US equity earnings announcement calendar: report date, before/after-market timing, analyst EPS estimate + count, market cap, and prior-year actual EPS. Sourced live from Nasdaq's public calendar. **Example:** `/v1/earnings-calendar?date=2026-07-14&days=3` Use when you want upcoming US earnings dates, timing and analyst estimates. Not for macro events (use macro_calendar) or filed reports (use filings_search). Behavior: read-only. Priced via x402 (USDC on Base) or free with WICKEDAPI_API_KEY; with neither, you get HTTP 402 with the decoded price in payment_required (a price quote, not a failure).
    ConnectorNo auth
  • Analyze one stock, or check one chosen pair of stocks. One stock: HMM regime detection, Hurst exponent, Bollinger/Keltner squeeze, Monte Carlo forward simulation. A pair (`ticker` and `ticker_b`, e.g. KO and PEP): whether the two hold together for spread trading. The QuanterLab pairs check rates the evidence that the two prices hold together as strong, mixed or weak, with a score out of a hundred, from the Engle-Granger and Johansen cointegration tests, the spread's half-life, how much the hedge ratio moves, and how often the two stocks share a market regime. It is the check to run when someone asks "is X / Y a tradable pair?" about any two stocks; `start_pairs_scan` searches a whole index for pairs instead. 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. An analysis takes about 30 seconds to 2 minutes. The call returns `{task_id, status, kind, dashboard_url}`; `get_regime_analysis_progress` reports progress and, when it has finished, carries `result`: for one stock, the regime now and how long it has run, volatility against the stock's own history, how the stock behaves (trending, mean reverting or a random walk), its trend and its drops, rounded; for a pair, how strong the evidence is that the two hold together and the check's score, the cointegration tests as p-value bands, the spread's half-life, the hedge ratio's variation, the correlation, and how often the two shared a regime, rounded. Unlike `start_regime_optimization`, which uses HMM regimes to grid-search trading thresholds, this analysis is descriptive. Args: ticker: Stock symbol (uppercased). Required. ticker_b: Optional second ticker; with it the analysis checks the pair (`ticker` / `ticker_b`) for spread trading. mode: Optional. `'volatility'` runs only the squeeze module. years: Lookback window in years (default 2). params: Optional dict overriding module-specific knobs. Most useful: `hmm_enabled` / `hurst_enabled` / `squeeze_enabled` / `mc_enabled` (disable modules); `hmm_states`; `mc_simulations`. 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 progress answer also carries `report_url`: the analysis written up as a QuanterLab report (the market states and their spells, or for a pair the checks of whether the two hold together). 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`.
    ConnectorOAuth
  • Return the complete recent-ideas report in one call. Call once with window (default 24h) and, only when the user asks for them, sections, sectors, source_type, direction, table_limit or detail_limit. Do not pass delivery, limit, cursor or offset. The server returns the whole report in one response and ignores delivery=paged on a first call; it pages only an oversized report. Only when a response has pagination.has_more=true, call again with its exact next_cursor alone until has_more=false; retain every page. Only the final page includes summary_context. Ranking and selection are final on the server. Present the tables as supplied and summarize thesis prose only for the detailed tickers, without grading theses, rejecting rows or recalculating scores. Read agent_guide and summary_context.analysis_instruction in full. Defaults: six sections, ten table rows and three unique details per section. One selected section renders one table without tabs, for example sections=["alpha_calls"], sectors=["Information Technology"]. The server applies sectors before loading ideas and skips unselected rankings. All six sections require a finite positive entry price for the instrument. Only selected detail tickers load thesis prose; detail_limit=0 needs none. Alpha ranks are final: 30% attention, 30% support, 25% price, 15% authors. Counts cover the full sector/source/window scope. direction selects ranking rows without removing opposing counts or evidence: Alpha/Consensus use the dominant direction, mention tables require a matching author stance within the query window (Spike also the matching side), First Calls uses the selected call's direction and Shorts a current author with that stance. Every table is ranked exactly like the site's Market Radar. Context 12.0.0/report format 9.0.0 includes effective report_options, selected section_order, full presentation rules, stored prices/returns/peaks and links. Detailed tickers do not repeat across selected sections. No external prices or bias/history recalculation is required. ticker_group_rows carry only the report tickers with their evidence (data_projection=report_tickers_with_evidence); summary_context.overview counts the whole window. Use get_recent_idea_candidates for a complete research export. Cursors pin all filters and report limits. The entire publication-time window must be within the last 7 days of current server time. Older or partly older windows are rejected, including signed cursor continuations and cached responses. Start a new request with a newer as_of or a shorter window if a snapshot ages out during pagination. Args: window: Exact lookback: 1h, 6h, 12h, 24h, or 1d. Default 24h. cursor: Leave empty; only the exact next_cursor while has_more=true. as_of: Optional ISO-8601 end boundary for a requested historical cutoff; the entire window must remain within the last 7 days. source_type: Optional twitter, youtube, newsletter, or reddit filter. direction: Ranking direction: long, short, avoid, close, trimmed, watch, neutral, or empty. delivery: Leave unset. paged is ignored on a first call. limit: Leave unset. Sizes only server-initiated fallback pages (1–200 ticker groups); NOT table size or a scan bound. offset: Deprecated; leave unset. sections: Nonempty selection of alpha_calls, top_mentions, mentions_spike, consensus, first_calls, shorts. Omitted/null selects all; canonical order. sectors: Sector names from the reviewed DB taxonomy; multiple names use OR. Case-insensitive; IT aliases Information Technology. Omitted/empty means all sectors, including unclassified tickers. Unknown names return the available sector names; Crypto is a sector, not an asset-type filter. table_limit: Rows per selected table, 1–10, default 10. detail_limit: Unique detailed tickers per selected section, 0–table_limit, default 3. Zero returns tables only; fewer qualifying rows stay fewer.
    ConnectorOAuth
  • List the website's stored AI insights: the precomputed cards on the AI Insights page, each a verified finding of one past analysis, newest analysis first and higher impact first. Each has its id, title, headline, category, impact, the days its numbers cover (window), the time the analysis ran (analyzed_at), its status (available, done, or discarded = hidden by the team), the team's rating, and its move's subject and metric. Call this first for an open-ended request for insights or for what to do ('give me some insights', 'what's interesting', 'what should I prioritize'), and answer from these cards instead of running a new analysis: highest impact first, each by its title and headline. Always state the window and the date the analysis ran, and offer a fresh look with the other analytics tools. Read one card in full with get_ai_insight. Paged: 20 by default; for more, pass limit (up to 50) and offset set to the returned next_offset until it is null. Default status is available. Returns status 'no_access' when AI Insights is not part of the organization's setup. Then, or when no insight is listed, answer from the other analytics tools.
    ConnectorNo auth
  • Use for what the market thinks of the player props in one game, not any one book's price: for each player and each line, the average implied probability (margin in) and the fair probability (margin out), with how many books each rests on. Only identical lines are combined, and a one-sided market such as anytime touchdown has no fair probability unless a book posts both sides. Latest pre-game prices. For each book's prices use get_player_props. Costs 10 credits. Prices are market information; no tool places, accepts or tracks wagers.
    ConnectorNo auth
  • Run forensic windows analysis (AACE RP 29R-03 §3.3, MIP 3.3 Observational / Dynamic / Contemporaneous As-Is) across multiple Primavera P6 XER snapshots and return the full analysis dict. This is the headline forensic tool — it computes per-window completion shifts, per-window slip registers (per-activity slip with a critical flag (total float of zero or less, or the driving path in a schedule with negative float)), per-window duration growth on critical-path activities, per-window per-party attribution (Owner / Contractor / Concurrent / Force Majeure / Unattributed), and cumulative project drift from baseline. The attribution math satisfies the CPP conservation check, per the AACE 29R-03 §3.3.E.13 requirement that the summed per-period net impacts equal the difference between the first schedule update and the last schedule update used in the evaluation (per-party day buckets sum to project drift within ±1 day, no cascade-double- counting). Use this tool for the full multi-window forensic claim. If you already have a windows result and only want the per-window × per-party grid view, call ``concurrent_delay_matrix`` instead. Args: schedules: list of dicts in chronological order. Minimum 2 entries (baseline + at least one update). Each dict must contain ``label`` (str) and EXACTLY ONE of: - ``xer_path`` — server-side filesystem path, OR - ``xer_content`` — full XER text content. Use ``xer_content`` when calling a hosted MCP server from a remote client whose XER lives locally. project_name: optional override; auto-picked from XER if "". baseline_idx: which entry in ``schedules`` is the contract baseline (default 0 = first one). entitlement_milestone: optional task_code (e.g. "Ready for Takeover") — recorded on the result, not used for math. company: optional, the firm the dashboard and the DOCX report carry (title block, print cover). Blank unless supplied, and blank carries no firm: a hosted run is the caller's document. output_dir: optional dir for HTML dashboard / DOCX report. If "", a tempdir is used and dropped after — the dashboard / report paths in the response will point to the temp location (caller responsible for moving them). Returns: { "analysis": full dict from run_windows() with keys: "windows", "cumulative", "baseline_label", "data_dates", "attribution_summary", "mcpm_attribution", ..., "dashboard": path to HTML dashboard (server-side), "report": path to DOCX executive report (server-side), "baseline_stability": {"worst_severity", "has_block", ...}, "data_date_corrections": the record of each update whose data date was moved to its latest actual, and of a baseline with actual dates after its data date ([] on clean files); each is also a data-quality warning "analysis"."criticality_basis": the schedules read by their driving path because they have negative float, and those beside them ([] when no schedule has negative float); the box they write is one data-quality warning } On failure: {"error": "..."} with no schedules processed.
    ConnectorNo auth
  • Corporate events: US SEC 8-K events, and official stock-exchange releases of Finnish and Swedish listed companies (from 2026-01-01: inside information such as profit warnings and large orders, management changes, tender offers, reports). Also the report calendar. Scopes: - ``"company"`` (default): one company's events, newest first; ``summarise=True`` returns per-type counts instead. Set since/until around a date to explain a price move. - ``"cross_company"``: events across companies filtered by event type, ``index="sp500"``, ``industry`` (substring), ``companies`` list or ``market="nordic"`` (default US). - ``"calendar"``: scheduled interim / annual report dates in ``since_date``..``until_date`` (default today .. +14 days, max 120), optional ``company`` / ``market``; ``published: true`` once the report is in Clarifo, ``include_published=False`` keeps only upcoming. Never extend the calendar with guessed dates. ``companies`` (up to 30) or ``portfolio_id`` (from portfolios) gives several companies in one call; ``coverage`` then says per company why it has no date (later_date_known, not_announced_yet, no_calendar_coverage). - ``"offerings"``: one US company's priced offerings (424B4 / 424B1 prospectus), the IPO first, then follow-ons newest first. - ``"ipos"``: recent US IPOs market-wide, newest first (default since: 90 days); SPACs are flagged ``is_spac``. Args: company: Name, ticker or CIK; required for company scope. since_date / until_date: YYYY-MM-DD (default since: 365 days for company, 30 days for cross_company, 90 days for ipos; none for offerings). event_types: acquisition, disposition, executive_change, director_change, material_contract, default, bankruptcy, covenant_breach, amendment, auditor_change, earnings, guidance_update, other; Nordic also inside_information, profit_warning, tender_offer, capital_event, major_shareholding, insider_trade, share_repurchase, agm. Nordic profit warnings and guidance changes are filed as inside information: read the titles. item_numbers: Raw 8-K items, e.g. ["2.01"] (US). limit: Max 500 (ignored when summarising). market: "us" or "nordic". portfolio_id: Calendar scope: the user's portfolio whose companies to list (from portfolios). materiality: Nordic only: "high" (inside information, tender offers, management changes; cross_company default), "medium" (+ reports, capital events, holdings; company default) or "low" (everything). Returns ``events[]`` (company and cross_company), ``summary`` (summarise) or calendar ``events[]`` (expected_date, period_label, confirmed, published). Nordic events carry ``title``, ``category``, ``materiality``, ``excerpt`` and ``source_url`` to the filed release (cite it). ``offerings[]`` / ``ipos[]``: offering_type, pricing_date, price_per_share, price_range, shares_offered, gross_proceeds_usd, exchange, ticker, underwriters, registration (S-1 / F-1), source_url; no coverage: ``diagnostic.reason = "no_offerings_data_yet"``.
    ConnectorAPI key
  • Create a Clarifo Automate automation, switched off. Nothing runs and nothing is spent until it is activated (activate_automation after the user approves, or in Clarifo). Use when the user asks for recurring research, e.g. a weekly watchlist brief. Show the user the returned summary (what, scope, schedule, timezone, next_run, folder) before offering to activate. kind=prompt reads only its watchlist (scope.company_count, scope.companies_sample): when the instructions name companies or a sector outside it, say which are not covered before offering to activate, and offer to add them to the watchlist (save_to_workspace) or a kind=reports automation with a sector, industry or market scope instead. Args: name: Short name, up to 60 characters. idempotency_key: Optional; leave it out. Clarifo recognises a repeated identical request by its content. Give one only to retry this same request. kind: "prompt" answers instructions across the watchlist on a cadence; "reports" drafts a cited document for each newly reported company in scope. instructions: For kind=prompt, what to answer (10+ characters). cadence: For kind=prompt: daily, weekly (default), monthly, quarterly. scope_kind: For kind=reports: all, market, watchlist, sector, industry, releases. kind=prompt reads watchlists only (all or watchlist); the result's scope says how many companies that is. scope_value: Market, sector, or watchlist (portfolio) id; for kind=prompt a watchlist id, or empty for every watchlist in the workspace. folder: Workspace folder for the output. run_times: Times of day, "HH:MM" in 15-minute steps (up to 6). run_days: ISO weekdays, 1 = Monday. timezone_name: IANA zone, e.g. "Europe/Helsinki", "America/New_York". max_new_per_run: Documents per run at most (1-25). language: Output language for kind=prompt: en, fi, sv. workspace_id: A workspace the user owns; omit when they own one. template: Optional; the name (or id) of one of the user's report templates, made in Clarifo under Automate > Report templates: a company-report template for kind=reports, a portfolio-report template for kind=prompt. Omit for Clarifo's standard format. An unknown name returns the available ones. Returns: {"status": "draft_created", "automation_id", "enabled": false, "what", "schedule", "timezone", "next_run", "activation_token", "review_url"} or {"error", "failure_kind"}.
    ConnectorAPI key
  • Change or pause one of the user's Clarifo automations, only when the user asks. Give only what changes; everything else stays. pause=true switches it off (it can be switched on again with activate_automation after the user approves its settings; this tool never switches one on). Confirm the change with the user first, then say what changed (before and the new settings) and give review_url. Args: automation_id: From automations. idempotency_key: Optional; leave it out. Clarifo recognises a repeated identical request by its content. Give one only to retry this same request. pause: True to switch the automation off. name: New name. instructions: For an instructions (prompt) automation: the new instructions it answers across the watchlist. cadence: For a prompt automation: daily, weekly, monthly, quarterly. language: For a prompt automation: en, fi, sv. scope_value: The watchlist (portfolio id) a prompt automation reads, or the market / sector of a report automation. scope_kind: For a report automation: all, market, watchlist, sector, industry. folder: Folder its documents go to. max_new_per_run: For a report automation: documents per run. run_times: For a report automation: run times, e.g. ["07:00"]. run_days: For a report automation: weekdays 1-7 (Monday = 1). timezone_name: IANA zone for the run times, e.g. "Europe/Helsinki". workspace_id: Optional; the automation's workspace. template: The name (or id) of one of the user's report templates of the automation's kind, or "standard" for Clarifo's standard format. keep_dashboard: true keeps a dashboard updated on every run: a watchlist (portfolio) automation keeps a portfolio dashboard per portfolio, emailed when the user's notification settings send Automate email; a report automation keeps an earnings-review dashboard per company. Returns: {"status": "automation_updated" | "automation_paused", "changed", "before", "automation_id", "name", "enabled", "what", "schedule", "cadence", "review_url"} or {"error", "failure_kind"}.
    Connector
    Destructive
    API key