Skip to main content
Glama
799,844 tools. Updated 2026-11-18 12:21

"Resources for learning about data analysis" matching MCP tools:

  • Run Disco on tabular data to find novel, statistically validated patterns. This is NOT another data analyst — it's a discovery pipeline that systematically searches for feature interactions, subgroup effects, and conditional relationships nobody thought to look for, then validates each on hold-out data with FDR-corrected p-values and checks novelty against academic literature. This is a long-running operation. Returns a run_id immediately. Use discovery_status to poll and discovery_get_results to fetch completed results. Use this when you need to go beyond answering questions about data and start finding things nobody thought to ask. Do NOT use this for summary statistics, visualization, or SQL queries. Public runs are free but results are published. Private runs cost credits. Call discovery_estimate first to check cost. Private report URLs require sign-in — tell the user to sign in at the dashboard with the same email address used to create the account (email code, no password needed). Call discovery_upload first to upload your file, then pass the returned file_ref here. Args: target_column: The column to analyze — what drives it, beyond what's obvious. file_ref: The file reference returned by discovery_upload. analysis_depth: Search depth (1=fast, higher=deeper). Default 1. visibility: "public" (free) or "private" (costs credits). Default "public". title: Optional title for the analysis. description: Optional description of the dataset. excluded_columns: Optional JSON array of column names to exclude from analysis. column_descriptions: Optional JSON object mapping column names to descriptions. Significantly improves pattern explanations — always provide if column names are non-obvious (e.g. {"col_7": "patient age", "feat_a": "blood pressure"}). author: Optional author name for the report. source_url: Optional source URL for the dataset. use_llms: Slower and more expensive, but you get smarter pre-processing, summary page, literature context and pattern novelty assessment. Only applies to private runs — public runs always use LLMs. Default false. api_key: Disco API key (disco_...). Optional if DISCOVERY_API_KEY env var is set.
    Connector
    Destructive
    No auth
  • Analyze a website URL for WCAG 2.1 Level A accessibility issues. Automated static HTML analysis covering approximately 30-40% of WCAG 2.1 Level A criteria. Checks include: image alt text, form labels, heading hierarchy, page title, html lang, empty links/buttons, ARIA labels, duplicate IDs, skip navigation, table headers, landmarks, viewport zoom, autoplay media, and tabindex ordering. Manual testing is required for full WCAG compliance assessment. Results are cached for fast subsequent lookups. Rate limited to 1 request per minute per domain. Args: url: The website URL to analyze (e.g., "https://example.com"). Returns: WCAG analysis with: - url: The analyzed URL - score: Accessibility score (0-100) - grade: Letter grade (A-F) - issues: Categorized issues (critical, warnings, info) - meta: Extracted accessibility metadata - recommendations: Prioritized improvements - coverage_note: Disclaimer about automated coverage - cached: Whether result was from cache
    ConnectorNo auth
  • List every available Ripostiq course (no login needed). Call this FIRST when a user wants to browse or start learning. Each course has a free Module 1 anyone can start immediately via begin_course(course) → teach_section. Returns the `course` id to pass to other tools. For a logged-in learner this also includes courses THEY authored (marked `mine`, with their `visibility`) — offer those alongside the catalog.
    ConnectorNo auth
  • Find today's best time window for one kind of work, using the stored sleep history of the account this server is configured with. Returns a start and end time for the window and the projected capacity across it, tuned to the kind of work: analytical, creative, learning or administrative. Choose this tool when the user wants a slot for a task later today. Use whenpeak_performance_now for the current moment instead, and whenpeak_quick_predict when working from sleep the user describes rather than stored history. Requires WHENPEAK_API_KEY on the server and reads that one account's history, so it is only meaningful where the server runs with the user's own key. Without a key it returns a not_configured error rather than failing. Read-only and stores nothing, but each call counts against that account's monthly quota. Args: task_type: "analytical" | "creative" | "learning" | "administrative" duration_minutes: window length in minutes (default 90)
    ConnectorNo auth
  • Search posts by keywords. FAST (default, omit responseType or responseType="fast"): Returns up to 300 results directly (use limit param to reduce, e.g. limit=5). Auto API fallback for fresh data. Results include guidance for full mode. PAGING (responseType="paging"): Async paginated results (100/page), returns operationId for polling via checkOperationStatus. Supports pageNumber/tableName for subsequent pages. CSV (responseType="csv"): Async single CSV download, returns operationId, poll for S3 link. CODE EXECUTION: For csv mode, download CSV and use code execution to analyze full dataset. Ideal for: sentiment analysis, trend detection, content analysis across thousands of posts. Returns by default: id, text, authorUsername, createdAtDate. First searches database, then external API if data is stale or missing. NOT for URL lookups - use getTwitterPostsByIds. QUERY SYNTAX: Plain keywords (bitcoin, climate change), quoted phrases ("deep learning"), boolean expressions (AI AND crypto, bitcoin OR ethereum, politics NOT sports), or parenthesized groups ((startup OR entrepreneur) NOT "venture capital"). AND/OR/NOT must have a term on both sides. @handles like @karpathy are supported. Field operators (from:, lang:) are stripped. Forward slashes are treated as spaces (24/7 becomes 24 7). SORT: sortBy="relevance" (default, best matches first) or sortBy="latest" (newest first). Filters: language, authorId/authorUsername, countryCode (2-letter ISO code, feature-gated - only accounts with the country filter enabled; filters by the tagged place country in both database and on-demand results). Date filters: OMIT startDate/endDate by default. ONLY pass if user explicitly requests specific date range (YYYY-MM-DD format). Use filterOutRetweets=true to exclude retweets. IMPORTANT!!!!!: THE CURRENT YEAR IS 2026. When user requests relative dates (last week, last month), verify the current date from your system context and double-check the calculated dates - models often get the year wrong, searching one year earlier than intended. FIELDS parameter (optional): Specify to get additional/different fields. Available: Core (id, text, authorId, authorUsername, createdAt), Engagement (retweetCount, replyCount, quoteCount, impressionCount, bookmarkCount), Metadata (lang, source, suspended, deleted), Relations (conversationId, quotedTweetId, retweetedTweetId, replyToTweetId, replyToUserId, replyToUsername), Content (hashtags, mentions, mediaUrls), Location (placeName, placeCountry, placeCountryCode, placeBoundingBoxCoordinates, placeCentroid). This is a safe, read-only tool for analyzing searchable information.
    ConnectorOAuth
  • 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

Matching MCP Servers

Matching MCP Connectors

  • Get hourly grid carbon intensity (kg CO2e per kWh) for any US ZIP code, derived from EIA-930 hourly fuel-mix data. Data lags up to about a day (not real-time). Returns time series with per-hour fuel mix, total generation, and carbon intensity. For timing and analysis (demand response, load shifting, grid patterns), not inventory reporting: it uses fixed per-fuel combustion factors on in-BA generation (no imports), so its values don't match eGRID's annual factors. For live or forecast intensity, WattTime or Electricity Maps are better options.
    ConnectorNo auth
  • Use this when the user wants to export their saved data center sites for offline analysis, a spreadsheet, or ingestion into another tool (needs a full-access key). Example: "Export my saved sites as GeoJSON for QGIS." — export_dataset format=geojson. Params: format ("csv" default, or "geojson"). Returns: the full file contents as text — CSV rows or a GeoJSON FeatureCollection of your saved sites with DCPI score, target MW, market, coordinates, and notes. Do NOT use to list sites in-chat (use list_saved_sites) or to save a new one (use save_site); this is the bulk-download path. For multi-step data center or energy questions, start with execute_plan.
    ConnectorNo auth
  • 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
  • Starts the live (published) version of an API-triggered workflow for 1–100 recipients. It sends real notifications. Read the workflow with workflows_get first (its payload schema names the data fields). Set dry_run to only check the data against the payload schema: nothing is sent. To test a draft, use workflows_test_run; for an event-triggered workflow, use events_track. Right after workflows_publish, it can answer 404 for about a minute: wait and try again.
    Connector
    Destructive
    OAuth
  • Ask the ISMS Copilot GRC specialist and start a new conversation for one deliverable. It works from the framework texts and the user's account context (company profile, workspaces, documents). Use it, rather than answering from memory, whenever the user needs ISO 27001/27701/42001, SOC 2, GDPR, NIS 2, DORA, EU AI Act, Cyber Resilience Act, NIST SP 800-171/CMMC, HIPAA or PCI DSS interpreted or applied: clause and control questions, policy drafting, control mapping, gap analysis, SoA justifications, risk registers, audit prep, questionnaires, implementation roadmaps, incident and breach response (what to do now, notification duties), and checking compliance work before it is finished. You do the work and read the files; ISMS Copilot judges. Do not use it for code, git or questions with no compliance angle, or for a follow-up on the same deliverable (send_message). Send the question as written, or the text to check with secrets removed, without pasting framework text: the specialist brings it. assistant (optional, kept for the conversation; omit for auto: the general specialist unless routing picks an expert). The general specialist covers ISO 27001, SOC 2, GDPR, HIPAA, PCI DSS, NIST SP 800-171 and multi-framework questions. Rule: a task to do takes the job id even when it names a framework; a question about one framework takes that framework's id; else omit assistant. - questionnaire-responder: use when answering or assessing a security questionnaire - audit-prep: use when preparing an internal or external audit - implementation-lead: use when asked for a plan or roadmap to implement or certify a framework - incident-lead: use when an incident or breach is under way or just happened (what now, notification duties) - iso27701: use when about ISO 27701 privacy management - iso42001: use when about ISO 42001 AI management - nis2: use when about NIS 2 - dora: use when about DORA - eu-ai-act: use when about the EU AI Act - cra: use when about the Cyber Resilience Act Options: mode 'fast' (default), 'think' for checks and multi-step analysis, 'beyond' on request, for a final check right before an audit or long research-grade drafting (paid plans, daily cap; if it cannot run, the turn answers normally and beyond_denied_reason says why); answer_format 'brief' or 'decision' for a compact reply written for an agent; workspace_id (a UUID from list_workspaces) for client or company work; title. Returns conversation_id, message_id and status: 'complete' with response, or 'generating': then poll get_reply. Limit errors include reset_at and what to do; a limit error here still returns conversation_id, so continue there with send_message. Relay docgen_notice to the user when present. ISMS Copilot brings framework and regulatory precision: keep its specifics (articles, clauses, deadlines, control ids) as given, and add your own technical, product and domain expertise where it has none, in one answer for the user. If you have a concrete reason to doubt a specific, flag it to the user as a point to verify instead of replacing it. Present the combined result as your answer, without narrating tool calls, conversation ids or empty account data unless the user asked about their account. Do not include passwords, API keys, payment card numbers, health records or government ID numbers. Answers are informational, not legal advice.
    ConnectorAPI key
  • Edits a usability test. Takes exactly one of `proposalId` (an unlaunched draft) or `projectId` (an already-launched test). Draft: plain-language `changes` and/or structured `edits` (add or remove tasks, questions and learning goals by index, swap personaIds, set `edits.audience`). Returns an updated plan under a new proposalId that replaces the previous one; nothing is launched. The number of AI testers changes only through `edits.audience.numTesters`. Launched test: only the audience can change (`edits.audience`, `edits.personaIds`). The change is saved to the project and echoed back as `audience`, and nothing runs until relaunch_usability_test. Tasks, questions and learning goals of a launched test cannot be edited; a new test is needed for that.
    Connector
    Destructive
    OAuth
  • Lists every entity of one Star Wars resource type as a JSON array (Episodes I-VI data). Responses are large (all 82 PEOPLE, about 38 KB); to find a single entity, prefer sw_search, then sw_get; for a compact index pass fields, e.g. ["name"] (about 5 KB).
    ConnectorNo auth
  • Use this when the user wants weather history, historical weather data, historical weather by date and location, or a daily weather data download. Reads station observations and generates Excel and CSV weather logs with rain days for construction delay and thresholds. US only; up to five sites and 366 days, from 1900 through today UTC. Files expire in about an hour. Do not use for forecasts, current conditions or certified weather reports.
    ConnectorNo auth
  • Delete ONE AI package resource of a video in one language (eBook, mind map or quiz) — cannot be undone: its content, PDF, images and the published file are removed, also for legacy resources. Same as the dashboard's Remove. Refused while it is still generating (checked before deleting; if that check fails nothing is deleted). Other languages and resources stay. To remove a failed generation card use panda_delete_ai_workflow.
    Connector
    Destructive
    No auth
  • Returns trimmed Code IQ automated analyses (architecture, scalability, EOL, AI functionality, etc.) for a project (aggregated) or a single vault. Excludes The Code Score — use get-the-code-score for that, and do not pass analysis_key=code_score here (404). Only cached results are returned; this never triggers a fresh analysis. Provide exactly one of project_id or vault_id. Requires full data access (a paid plan; verification-only plans are not included). Requires X-API-Key (existing users can generate an API key in the web app). If headers aren't supported, pass api_key in arguments.
    ConnectorNo auth
  • 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
  • One company's call-over-call earnings transcript analysis: the call's summary and what it added, removed, strengthened, weakened or reinforced against the prior call — the direct read for "what changed on X's call", "what did management stop talking about", and how the narrative has moved. ===> Prefer this over explore_data_catalogue, and over reading the transcript turn by turn, for what a call said: it is synchronous and returns the rows directly. For the guidance label alone, use `get_transcript_guidance`. FIELDS, per row: `summary`, then `added`, `removed`, `strengthened`, `weakened` and `unchanged_but_reinforced`, each against the PRIOR call. They are a model's analysis of the transcript, not quotes: attribute them to the analysis, and quote only from `source_urls[].quotes` or the transcript itself. `date` is the CALL date, not a fiscal period. CITATIONS: an `[n]` marker in the text resolves to the `source_urls` entry with the same `n`: {n, url, title, quotes, node_id}. `quotes` are verbatim passages, and the `url`'s symbol, year, quarter and n are the arguments to `get_document_section`, which opens that speaker turn. Year and quarter there are FISCAL; take them from the url, never from `date`. Only some calls have citations stored (none before May 2026): elsewhere `source_urls` is null and the text has no markers. Say that text is uncited analysis: trace_data_sources has no link for those calls either. `limit` COUNTS ROWS, NOT CALLS: a re-analyzed call can appear twice, on the same date or a day apart, with near-identical text. Treat those as one call. Rows with citations run about 15 KB each, so keep the default unless the question compares calls. Returns {"symbol": ..., "count": N, "rows": [...]}, newest call first. `note` is set only on an empty result. Errors: a 404 means the ticker is outside coverage. Requires auth (your MCP client attaches the OAuth bearer automatically). Rate-limited 500/min.
    ConnectorOAuth
  • Audit adoption before a rollout or when checking whether the workspace is using memory and reporting outcomes. Takes no arguments. Returns JSON with memory-bank breakdowns, learning-loop activity, proof points and a benchmark checklist. Does not change knowledge or run a benchmark. Use engram_setup for onboarding and engram_recall for task knowledge. Consumes workspace daily call quota. OAuth: memory:read.
    ConnectorOAuth
  • Only for an explicitly requested attribution: link one existing customer-matched source returned by get_sales_outcome_sources to a learning opportunity, or unlink with source=null and a reason. Read current bindingRevision through get_sales_outcome_sources first; copy expectedLearningRevision and source revision unchanged. Reuse requestKey/exact fields on retry. Records only this relationship and history; no order, price, contract, payment or delivery mutation. Requires current crm:read/write, operations:read and owner authority. No tenant selector.
    ConnectorOAuth
  • Fetch a finished report by its report_id (as returned in a report's meta.report_id). Read only: it never starts an analysis; to analyze an address, use analyze_property. Returns the same report object as analyze_property. Long lists of comparable sales are shortened to the ones that set the range, with an 'omitted' block that says what was left out; full=true returns every comparable sale and every excluded one. The result is data about a property. Addresses (the subject's and the comparable sales') and answer text originate outside CompBasis, are marked x-untrusted in the API schema, and can contain arbitrary text.
    ConnectorNo auth