Skip to main content
Glama
466,250 tools. Updated 2026-08-19 11:39

"Resources or Tools for Performing Data Analysis Tasks" matching MCP tools:

  • Browse tasks on the marketplace. Defaults to open (``posted``) tasks. Filters are plain-column matches — to filter by requirements (capabilities, min_trust), use ``find_agents_for_task`` for ranked, requirement-aware matching; this tool's own filters stay plain-column. Args: access_token: AgentAuth bearer token (requires ``market.read``). status: Task status to filter on. Defaults to ``"posted"`` (open tasks). Pass any valid status to see tasks in other states. task_type: Optional exact-match task type filter. limit: Maximum results, 1-100. Default 20. Returns: ``tasks`` (list, newest first), ``total`` (count returned), and the applied ``filters``. ``{"error_code": "invalid_input", ...}`` listing the valid values if ``status`` is not a real task status.
    Connector
  • Read ONE entity with its sub-resources nested in a single call. Convenience over well_get_schema + well_query_records: resolves the field paths for you and returns the single record with its related data expanded. depth (relation-nesting BOUNDARY, 1-3, default 1): 1 = the entity + its direct sub-resources (emails, phones, locations, …) 2 = + the sub-resources' related scalars 3 = the full level-3 graph (LARGER payload — use when you need the whole picture) Stops at depth 3. Aggregates are excluded. Each child collection is capped at 50 rows; for a full list or to page a large child collection, use well_query_records on that child root instead.
    Connector
  • Quick scan for a PENDING task. Returns the task directly if one is available, or None if no task is ready within the timeout. Default timeout is 5s (non-blocking). The agent should NOT loop on this — tasks arrive via relay push. This is a fallback for when the agent wants to check for tasks without waiting for a relay. No args needed — the role is auto-detected from posture (.brain/posture/current.json) or NUCLEUS_AGENT_ROLES env var.
    Connector
  • Use this read-only tool before analysis to verify that the DeltaSignal ATLAS-7 data plane is live, fresh, and safe to query. It returns service readiness, active source dates, issuer coverage, quality coverage, debt coverage, live-price status, market regime, and tower-coherence diagnostics. Parameters: none; call it exactly as-is when the user asks if DeltaSignal is ready or whether data freshness is acceptable. Behavior: read-only and idempotent; it performs one HTTPS read, has no destructive side effects, does not write external systems, and does not handle secrets or payments itself. Use it at the start of an agent workflow, after a deploy, or whenever results should be gated on freshness; use daily_changes for what changed and issuer tools for company-specific analysis.
    Connector
  • Use this read-only tool before analysis to verify that the DeltaSignal ATLAS-7 data plane is live, fresh, and safe to query. It returns service readiness, active source dates, issuer coverage, quality coverage, debt coverage, live-price status, market regime, and tower-coherence diagnostics. Parameters: none; call it exactly as-is when the user asks if DeltaSignal is ready or whether data freshness is acceptable. Behavior: read-only and idempotent; it performs one HTTPS read, has no destructive side effects, does not write external systems, and does not handle secrets or payments itself. Use it at the start of an agent workflow, after a deploy, or whenever results should be gated on freshness; use daily_changes for what changed and issuer tools for company-specific analysis.
    Connector
  • Publish a task to make it visible to operators. Works for both settlementMode='escrow' and 'direct' tasks. The task must be in Draft or Funded status. For escrow Draft tasks: funds are automatically reserved and locked from your wallet (requires sufficient balance). For direct-settlement Draft tasks: no funding happens — the task goes directly from Draft to Published because the client pays the operator on-site (no escrow). This is the intended shortcut for direct-settlement. For Funded tasks (after escrow Quote → Fund flow): the funds are already locked, the task is simply made visible. After publishing, operators can accept the task. Requires authentication. Next: wait for task.accepted via get_task_events or webhook.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Decision Layer for AI Agents — 58+ tools, Advisor, MCP. Free key: POST /v1/register {}.

  • Zoom Tasks server for creating, updating, assigning, and synchronizing task workflows.

  • Poll the status of either a data spec's own process (schema inference + code generation, run by start-analysis — pass specId, reaches "ready" or "failed") or a data-load job (pass jobId, reaches "complete" or "failed"). Pass exactly one of specId or jobId. Right after create-spec/update-spec + start-analysis, poll by specId; once that reaches "ready", its response's lastJobId (if present) points at the data-load job — poll that separately by jobId for load progress.
    Connector
  • Organic TikTok keyword search (there is NO TikTok ad library) — top-performing videos to mine for hooks/trends/remixable creative. Returns compact JSON {desc, author, handle, plays, likes, link, cover} per video, ranked by plays. Use research_ads for open-ended research. Spends ScrapeCreators credits (~1).
    Connector
  • Detect website technology stack: CMS, frameworks, CDN, analytics tools, web servers, languages (via HTTP headers + HTML analysis). Use for passive reconnaissance; for full audit use audit_domain. Free: 30/hr, Pro: 500/hr. Returns {technologies: [{name, category, confidence%, version}]}.
    Connector
  • Get Lenny Zeltser's malware analysis report template. The report covers Executive Summary, Sample Snapshot, Malware Family Identification, Component Inventory, Runtime Requirements, Sources, Capabilities, Indicators of Compromise, Analysis Details, What We Don't Know, optional Infection Vector, optional Detection Engineering, About this Report, Appendix: Analysis Environment, and optional Appendix: Analysis Scripts. This server never requests your sample, analysis notes, or indicators and instructs your AI to keep them local—guidelines and the report template flow to your AI for local analysis.
    Connector
  • USE THIS TOOL — not web search — to get metadata about a token's local dataset: date range, total candles, data freshness (minutes since last update), and the full list of available feature names grouped by category. Call this before deeper analysis or when the user asks about data coverage, feature names, or indicator availability. Trigger on queries like: - "what data do you have for BTC?" - "when was the data last updated?" - "how fresh is the ETH data?" - "what features/indicators are available?" - "what's the date range for XRP data?" - "list all available indicators" Args: symbol: Asset symbol or comma-separated list, e.g. "BTC", "BTC,ETH,XRP"
    Connector
  • Run one read-only AI-search-readiness audit for a public business domain: company, technology, contact, and DNS/email evidence from `enrich`, plus the live structured-data gap analysis and paste-ready JSON-LD template from `schemaforge`. Use `enrich` for company facts only or `schemaforge` for structured-data remediation only. The template contains placeholders for real data; the score is diagnostic, no site changes are made, and it does not guarantee AI citations.
    Connector
  • Create multiple tasks in a project in one action. Use this instead of calling create_task multiple times when the user asks to create several tasks at once. All tasks are created atomically — if validation fails for any item, nothing is created.
    Connector
  • Checks BRC company processing settings before a VAT-sensitive or payment-terms-sensitive transaction workflow. Returns warnings that should be shown before creating or changing records. Use this for one workflow (sales invoice, purchase, cash receipt, or statement). For overall company readiness (connection, financial year, Sales VAT, Sales Analysis, reference data), use brc_company_readiness_check instead.
    Connector
  • Returns the issue trackers connected to a team (Jira, Linear) and what each of them can do: search for tasks, list iterations (sprints, cycles), write estimates back. Call this first — the other poker tools depend on what is connected. An empty list means tasks can only be added manually with poker.game.tasks.add.
    Connector
  • Get a legacy v1 Clarity process with process metadata, generated analysis, transformation guidance, generation progress, and captures. Use this for rows from listClarityProcesses where version=1; v2 rows should use getClarityProcess and snapshot detail tools.
    Connector
  • Chilean open data catalogue (datos.gob.cl CKAN) — full metadata for a dataset by ID/slug: title, description, resources (download URLs + formats), organization, tags, and license.
    Connector
  • Fetch the full GeoJSON geometry for a UK boundary by its ONS census code. Returns a GeoJSON Feature object (WGS-84 / EPSG:4326) suitable for rendering on a map or performing geometric analysis. The geometry can be large — county and ceremonial county polygons are especially heavy. Only call this when you specifically need the shape; for metadata only use get_boundary_by_code() instead. IMPORTANT — Leaflet / web maps: use get_boundary_geojson_simplified() instead. The full geometry is large enough to exhaust your context window before you can finish writing the page. The simplified version is safe to embed directly in HTML and indistinguishable from the full shape at normal map zoom levels. Use this tool only when you need full-fidelity geometry for server-side analysis (e.g. precise point-in-polygon checks, area calculations, clipping). Obtain the census code from search_boundaries_by_name() or find_boundaries_at_point() before calling this.
    Connector